Net user returns "... completed with one or more errors."

oxonsi said:

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

Bree said:

@Kari, isn't the net user message "The command completed with one or more errors." referring to not being able to display the computer's name?

... and my instructions are precisely attacking that issue, forcing OOBE to be run and new computer name to be generated.

The play with usernames is only to assure that existing user account will also work after the Sysprep. It has a bad habit to disable Start and Search / Cortana from existing user accounts if left active. By using a Dummy account and setting existing accounts inactive, then sysprepping, we can be sure that this non-working Start and Search / Cortana will not happen.

My instructions do nothing else than forces Windows to set a new computer name, resets Event Viewer and restore points.

oxonsi said:

Thanks for the replies.

I will make the image file backup before attempting anything further. I am in the habit of using Macrium Reflect to image my machine, but it has been about a week since my last full image backup, so this is a good time to do so in any case.

I appreciate the info. I'll probably try the less "intrusive" methods of renaming first. I think I now have enough information to resolve this one way or another.

Thanks all!

The method I described is not at least intrusive. It keeps everything intact but as it runs OOBE again, a new computer SID and PC name will be generated, which I am 99% sure will resolve your issue. Worst case scenario is that you get same error but at least this method allows you to change the PC name when done.

Anyway, your PC, your decision. We can first spend a few days here trying to find another way.

oxonsi said:

I have a new image file backup.

Here's what happened when I executed Sysprep. You can tell me what I may be doing wrong [or that my PC is crazy]... At the initial OOBE screen, it assigned the name System. There was small link toward the bottom of the screen that said, "I'm not System", so I clicked on that. Then it asked me the usual questions about privacy settings [custom setup selected, not express]. And then it finally asked me to login as Dummy1. There was no option to create an initial user account as Dummy2.

Is this normal? Anyway around it so that I can create Dummy2 as an initial user account?

Thanks for all the help!

No, that's OK. In that case you don't need "Dummy2".

Just reactivate your old user accounts, sign in to your original admin account and see if you can change the PC name. If yes, then check what NET USER says.