Right, I was getting lazy. Probably should have stated, "that is my problem, or at least one of my problem(s)"... Logic :)
When I attempt to rename, I receive the message, "The PC name is invalid." no matter what name I choose. And if I enter the current name, it tells me I need to choose a different name.
It certainly appears there is a problem with my PC's name. Any idea how I might remedy that?
This should work:
1.) Create a new local user account, name it as you wish. I use username
Dummy1 here. Make this account an administrator account.
2.) Sign out from your normal user account, sign in to the new Dummy1 account.
3.) Open an elevated
Command Prompt, disable all existing user accounts except the new one you are currently signed in with following command:
Code:
net user USERNAME /active:no
4.) Press
WIN + R to open
Run prompt, type following command and hit
Enter:
Code:
%windir%\system32\Sysprep\Sysprep.exe /oobe /reboot
5.) This runs Sysprep forcing Windows to go through the initial
OOBE (Windows Welcome Mode, setup) again,
generating a new PC name. You will go through the normal OOBE and need to create an initial user account. You cannot use any username already existing in system, I use
Dummy2 at this point.
6.) When on desktop of
Dummy2, open elevated
Command Prompt and re-activate your temporarily disabled old user account with following command:
Code:
net user USERNAME /active:yes
7.) Sign out from
Dummy2, sign in to your old, normal admin account
8.) Remove
Dummy1 and
Dummy2 accounts
That's it. I'll bet your NET USER command will return no more errors.
BTW, although I am extremely familiar with Sysprep and how it can be used (no bragging, just stating a fact) I would never run it on an existing installation without creating a system image backup first. The above instructions will work but in case you come back telling you can't boot anymore after following the instructions, I will tell you to restore the systsme image you made before proceeding.
If at that point you tell me you don't have a system image, you can only blame yourself. My only response to that would be "Tough!".
The above flow of actions takes 3 to 5 minutes, not counting the time to backup your system first.
Kari