Main Forum > Tweaking.com Support & Help
Win 1803 ran Tweaking, now windows update does not work on both laptops
Boggin:
I'll pass this on as it still seems to be happening, but given the few who have experienced this and I have been unable to replicate it on my Win 10 - I'm not sure if the cause can be nailed down.
If the program's registry restore facility doesn't get you back to where it was then I suggest you also perform a repair install.
What was the reason you ran the repair program ?
AlphaStealthHWSW:
OK, I now have a third PC that was updated to 1803, worked fine including update function, then I ran Then Windows Repair Tool and now that third PC gives me an error on update. Sadly I tried to do a DISM repair and that did not work (this time). The first PC was repaired by doing a clean install. The second PC had unrepairable issues when SFC was run but did fix all the issue when a DISM repair was run. It looks like I am going to have to do a clean install on this third PC...I wish the admin at Tweaking.com would recognize that the tool is causing an issue on 1803 systems. Too many of us have had the same issue...
Boggin:
--- Quote from: AlphaStealthHWSW on June 02, 2018, 10:00:44 pm ---OK, I now have a third PC that was updated to 1803, worked fine including update function, then I ran Then Windows Repair Tool and now that third PC gives me an error on update. Sadly I tried to do a DISM repair and that did not work (this time). The first PC was repaired by doing a clean install. The second PC had unrepairable issues when SFC was run but did fix all the issue when a DISM repair was run. It looks like I am going to have to do a clean install on this third PC...I wish the admin at Tweaking.com would recognize that the tool is causing an issue on 1803 systems. Too many of us have had the same issue...
--- End quote ---
Can you post the make & models of the computers affected and can I suggest you perform a repair install instead of a clean install.
A repair install doesn't affect personal stuff or installed programs so will be less time consuming.
AlphaStealthHWSW:
I had my third Windows 10 Pro 1803 PC develop this issue. It turned out I had a system restore file from just before the 1803 update, so I restored to that state and then ran the Windows Repair tool version that was part of the system, updated drivers and then updated windows up to and including the 1803 update (12 hours of effort). Everything checks out and works now, but I am reluctant to update and run the Windows Repair tool until I see a solution to this issue be released...
AlphaStealthHWSW:
"Can you post the make & models of the computers affected and can I suggest you perform a repair install instead of a clean install."
OK, the PCs effected are: 1) HP Touchsmart 300 AIO running Windows 10 Pro OS, 2) MSI GX70 3BE Laptop running Windows 10 Pro OS and 3) Brand new custom built Gaming PC (ASUS X370 MB, Ryzen 1800X, Samsung 960 pro 512gb, RX 560 GPU) running Windows 10 Pro OS.
As you can see they are all different HW generations and models running Windows 10 Pro OS. I have another 5 Windows 10 Pro 1803 PCs in the family that I am holding off running Windows Repair tool until I see a solution...
I ended up finding a pre-1803 system restore file and restored to that state - still took awhile - 12 hours...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version