New
#180
Who knows if it would be fixed by the April 11th release.
This issue caused by CCleaner which I don't use no more was never fixed and once again my PC was the only one affected. Nothing online even in the CCleaner forums and none of the other 3 PC's had issues too.
Windows messed up.
As I said if I avoid CCleaner I can prevent that ugly annoyance.
When I saw the Original Post I was super excited to give it a whirl... but then I saw the softpedia mention in one of the posts and my dog ears perked up, thinking: "uh-oh... this might get interesting".
Sorry you guys went through all that just to end up having to restore more than likely, bummer. I am not one with much patience either when it comes to new builds etc. so I understand the temptation, and the pain, but... the good news is that we're probably VERY close to seeing this in the update stream any time now so still a helpful post! :)
Good luck with the restores, although I'm sure you guys will be fine and have it down to a science.
It has nothing to do with an AV issue. It's simply a laptop thing as all my systems run the same version of Windows 10 x 64 Pro and all use Defender as an AV. Yet only the laptop gives me hell updating.
- Here's the Anniversary Update issue.
- Here's the Threshold update Issue.
And now, we have the Creators update giving the same issue... "Windows 10 installation has failed". In the past 2 instances, nothing worked but a clean install. On this, it looks to be the same. Kind of expected it but, was hoping someone along the way seen the same issue and figured out a solution by now.
BTW this only happens with major OS upgrades... TH, Anniversary, and now Creators. NEVER with regular updates, including cumulative updates.
Thanks.
Yesterday I posted about problems with the Creators Update and the virtualization program Shadow Defender so I thought I'd inform that I've heard from the developer, Tony, and he replied with the following:
Thanks for your feedback. There is a conflict between Shadow Defender and Win10 Creator Update. It will be solved in the next version.
Thanks.
Best regards,
Tony