Windows 10: Reset Windows Update in Windows 10

I'm glad it was able to help throkr. I hope you have a Happy New Year as well. *Smile

 

My Windows 10 PC came up with error code 0x8e5e03fa and it's now sorted by executing the .bat file and resetting everything. I had tried other options from other forums/sites with no luck.

This is the second time I end up here and I find the solution for my Windows problems! Great forum, I shall keep an eye on it!

Thank you for your help, appreciated!
Tony

 

You're most welcome Tony. I'm glad it could help. *Smile

 

I know this is it delay, but there is bug that happens when this done atlest every time I done it.

Doing this will reset your User Account from Admin to Standard depsite it saying it Admin, To fix this one has to open an admin CMD and run
net user administrator /active:yes

Sign out of computer go into the Administrator that is listed there go to User Accounts>manage account types you will notice it say ADMIN is selected ( its really not) pick standard hit apply go back into manage accounts types it will now show standard ( as it really is now) select Admin hit apply.

Account Type - Change in Windows 10

Sign out go back to your normal user name. open task manager will no longer prompt the uac window. from there you can open an admin CMD and run
net user administrator /active:no

to turn off that admin login

The bug seem to set users back to standard but it wont update GUI. I have now had to do this 3 times each time after the wu reset was used

 

I tried it had a hang on a update now cannot access anything administrative

Error after running then reboot
0x80070005

cannot login as admin, no access to users/groups etc

Keep getting unknown user wants to make changes to settings on everything I click


right clicked unblocked, ran as admin, .bak missing during run finished properly then rebooted just sitting in a endless loop on good install no options

 

Hello OdinSon,

Sorry to hear that. Doing a system restore at boot using a restore point dated before doing this will undo it.

System Restore Windows 10

 

The fix above works was posting then going in to reboot seen it after commented very nice save *Party

It happened to me everytime I ran as well, so it was basically knocking out user admin at end of the command, just enabled admin as tsunami2311 said and followed his path in comment viola it was set to standard.

His post is definitely a good addition thanks again seems this is not everyone must be something set different between users?

Thanks tsunami2311

 

Hi Shawn,

I was reading another thread that pointed me here and I have a question about your .bat file in post #1. The line just before the re-registering of .dlls is: cd /d %windir%\system32 and I'm wondering what effect that would have on my machine. I'm not having any problems, just curious.

If I read that cmd correctly the .bat file is requesting a change to the d directory to re-register the .dlls in the Windows / system32 folder(s).

My new Lenovo 110 ideapad has a d partition but it doesn't have a windows directory, Lenovo has it set up for drivers, the register folder you do see has a disable_AN file in it:




Here's a shot of my dskmgmt:





My DOS skills are really rusty but I'm hoping pretty sure you can clear this up for me. *Smile

Steve

 

Hello Steve @Anak, *Smile

The cd /d %windir%\system32 line is to change the command line directory to "C:\Windows\System32" to be able re-register the .dll files listed after that line in the bat file since the .dll files are located in the System32 folder.

To change the drive and the directory at the same time, use the cd command, followed by the “/d” switch. The /d parameter is used to change the current drive to a specific folder from another disk volume.

 

Thanks Shawn, @Brink,

Ahhh.... That's what was throwing me off, no drive before cd , I'm used to seeing C:> cd /D.

Let's see if I understand, in this case the .bat file never left the C: drive but it did use other directories and in order to re-register the .dlls you needed cd /d to move back to Windows\System32 to do it.

Sound right?

 

Correct. It was used to make sure the command prompt was using the correct directory for registering the .dlls.

 

Great! Thanks again Shawn, I can go to bed now. *Wink

 

Hello Shawn. Tuesday's WUs didn't change my build number from (1607) 14393.693 to 14393.953. Gerry Cornell over at the MS Community kindly recommended this article of yours. I'm about 0.75 on the MS "tech knowledge scale" but this was so easy to follow. It worked (with only one slight query - below) so thanks very much for once again coming up trumps. Much appreciated.

At the top, you show a 'before & after' comparison of Installed Updates & in the 'after' it's shown as empty. Is that what it should shown for everyone? Mine were identical but after re-setting the Failed WU (KB4013429) as now on the main Update screen - you have an Update ready to be installed (or whatever). I installed that so now it's AOK!

Spoke too soon. I'd been having problems inputting this. Slow response, delete, some character keys & space bar not working - had to key in slowly & carefully. Then this crashed, & it's happened six times now. Thank goodness for Auto-Save. If I don't get back within an hour it will mean I didn't have the problem elsewhere. But thanks!!

 

Hello @Taffy078, *Smile

How's it going so far?

If you have an update available after resetting, then it would be normal to see that when it checks for updates next.

 

Hi. When I first realised that my build number hadn't changed, my Update History showed the full list going back to 9th August 2016. The latest ones shown were:
Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429).Update for Windows 10 Version 1607 for x64-based Systems (KB4013418).Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB4014329).

Post resetting, it still showed the same info but on the preceding page Update Status (that was empty before) now showed that [Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429)]
Edited this at 14:40 to replace with Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB4014329) was now available. It all worked brilliantly bit I just wondered whether my Update History should have been blank, not full.

Oh, I had no problems on other site when keying in posts and I've had no problems with this one. Many thanks.