New
#20
Thank you Brink,
I did not know this procedure so I stupidly reinstalled.
At least I now control the installation
Thank you Brink,
I did not know this procedure so I stupidly reinstalled.
At least I now control the installation
No worries. At least a clean install would also usually iron out any other bugs you may of had.
That's an understatement! Yet the upgrade on the 7 Pro machine is doing well so far on a drive that is older then those in the main case! I previously ran Vista on the drive now seeing both a clean install of 10 that had been dual booting with 7 until the upgrade there. I might even toss a temp install of 7 Home Premium to see a 10Home upgrade/10Pro clean install dual boot and end up renaming the pc one more time!
Is renaming a computer cap and lower case sensitive? For instance, Is "BRINK-PC" the same computer name as "Brink-PC"?
I label my drives here as well as the PC name for each version having a 10/7 dual boot going. The default user name/number you see when first setting Windows up is automatically generated by the Windows installer and can always be changed easy enough.
The name can be all Upper, all Lower, or a mix up of both and even include numbers. Dashes, @ symbol is typically seen at times, and Underscores are seen while a few of the other symbols won't work there. Sometime I will have to get around to making up a list of the Dos and Won'ts.
I hope it's helpful to mention that with build 10586.17, unless a drive is ALL CAPS, a network may not see it. That, plus making sure the service function discovery resource publication is set to automatic solved that problem for me. Nevertheless, if you use lowercase to name a drive and it disappears from your network, try recasting the name in ALL CAPS to get it to reappear.
What is actually the maximal length for a Windows 10 computer name?
(I read that there are two limits according to https://support.microsoft.com/en-us/kb/909264
But Win10 let me enter a much longer name then 15 characters).