Main Forum > Tweaking.com Support & Help
Windows 10 build 1809 and WR (Make sure to use WR 4.4.0 or newer)
Shane:
OK so here is what I found in my testing, it wasnt any single repair breaking windows 10 1809, the antivirus or anything else. It was windows itself!
I found in my testing that 1809 has a bug where when you use the bcdedit command to set safemode with networking and then use the bcdedit to remove the command it doesn't fully work. Those are the commands my program uses to get windows into safe mode.
So what happens is 2 registry keys are created by windows when using bcdedit but when you remove the command the 2 registry keys are not removed! So windows thinks its still in safe mode when it isnt, and so no service that isnt allowed to run in safe mode will start! This means windows updates not opening, antiivirus not working all of it and a ton more. This didn't happen in older builds or older versions of Windows.
So in the new version of my program (v4.4.0 released today as of this post) I have WR set to remove those two registry keys! After that everything works great and the repairs arent actually breaking anything.
So if you get a user who has this trouble, there is a way to fix it! two ways actually.
1st way: Have them load up the new version of WR and have WR restart in safe mode, once in safe mode open WR and then simply close it. WR will remove the registry keys when it closes and then restart windows. This is by far the easiest way for users.
2nd way: In the program folder under the files folder and then the regfiles folder I made a remove_stuck_safemode.reg files that will delete the registry keys if they are there. All a user needs to do is double click on it and then restart windows. While this may seem easier, it also means telling some users how to actually find the file, which you know isn't always easy.
Keeping up with the constant changes and new bugs in every new build of Windows 10 is a challenge, thanks for hanging in there with me!
-Shane
u_i:
Running WR appears to damage irreversibly Windows Update for Win 10, as of Dec 2, 2018. I spent several days on it before identifying that WR (I believe 4.4.0) is the culprit. After running the basic subset of the repairs, Windows Update quits downloading files. Registry and Permissions restoration does not help. System Restore points seem to disappear after registry restoration. At this point I only get back to operation using partition backup from a month ago or so. At this stage I am unstalling WR to ensure that I do not activate it accidentally.
Boggin:
--- Quote from: u_i on December 02, 2018, 05:30:52 pm ---Running WR appears to damage irreversibly Windows Update for Win 10, as of Dec 2, 2018. I spent several days on it before identifying that WR (I believe 4.4.0) is the culprit. After running the basic subset of the repairs, Windows Update quits downloading files. Registry and Permissions restoration does not help. System Restore points seem to disappear after registry restoration. At this point I only get back to operation using partition backup from a month ago or so. At this stage I am unstalling WR to ensure that I do not activate it accidentally.
--- End quote ---
You should have opened your own thread about this as it is different to the original problem where machines were staying partly in Safe Mode with Networking.
However, although you are the only person to have reported this new problem, I will pass it onto Shane.
Can you go Start - type winver and press enter when it comes up and let us know the exact version of Win 10 you are using.
While I've test run 4.4.0, I haven't experienced it remaining in Safe Mode but can't verify the problem with the updates as I'd restored with the Macrium system image I'd created before running the program.
u_i:
Apologies for the rushed posting, but since I was crippled by this and recovering took days of work - in particular trying to reset the Automatic Update to make it work and that led to nowhere - I thought I should warn others promptly. In any case, the system ius Windows 10 Pro 64-bit x64. Winver says version 1709 OS Build 16299.665. Before unistalling I had there Tweaking.com Repair Pro. After running the standard version of repairs, I think opening custom, but then without changing defaults, the Automatic Updates would be crippled, always coming back with an error from download of anything, never going above 0%. The claimed error numbers might vary, but never getting beyond 0%, please restart to fix etc. I think I applied all remedies from the Web for fixing the Update Assistant, but nothing worked. Manual updates would work with hiccups - not all update numbers from Update Assistant are actually posted on MS Update Central.
Boggin:
I've emailed Shane about your error report.
The current version that I have is 1803 17134.441 although some are at 1809 but that was pulled when it was found to be causing serious problems, so you should be up to at least 1803.
Updating from 1709 to 1803 took about 4hrs on my two Win 10 machines.
JFI some things you can try to manually fix updates is to open a Command Prompt (Admin) or Powershell (Admin) and enter these cmds, although you may have already tried these -
dism /online /cleanup-image /startcomponentcleanup
dism /online /cleanup-image /restorehealth
sfc /scannow
The sfc /scannow would tell you if any corruption remains.
The following cmds which you can copy & paste to the cmd prompt to auto run will reset the update components, but you may have to press enter for the last one to execute.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Enter exit to close the cmd window.
Navigation
[0] Message Index
[#] Next page
Go to full version