Windows update messed up my computer

Anonymous
2017-11-07T05:30:30+00:00

I saw this thing in the notification center that said something about a windows update. I can't remember exactly what it said or looked like. But I clicked on it and let it update and do it's thing.  

Then when it was done. I set the computer to restart and update. When it updated and restarted I started to have problems like the start menu refused to come up. And I could not start task manager. Task manager would just get a timeout error after a bit of waiting. I could not do anything from the taskbar except open file explorer. I tried waiting for 20mins and that didn't work. So I tried restarting a couple of times and that did not work.

Then I tried holding the shift key and restarting from the log in menu to try resetting it with a restore point and there was no restore points? I know I made restore points before the troubles started to occur?

So the thing that fixed it was this option to revert to a previous version of windows. 

In that menu that I got up from holding the shift key at windows login and restarting the computer. 

This is a brand new computer I bought from Costco. 

I would really like feedback from you. And want to know what you think? 

Is it happening to a lot of other people? Or just me so far? 

I really hope you can give me a good answer that would make me feel better about the whole thing!

I kinda freaked out and thought... what if I got a lemon!  :)

Moved from: Windows / Windows 10 / Windows update, recovery, & backup

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

69 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-17T05:42:10+00:00

    Microsoft will screw you.  Go Apple next time.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-21T13:20:07+00:00

    I also have run into problems, previous updates have in the past left my system in a non bootable state whereby I have had to fully reinstall Windows and start again. Now I choose to try and ignore the updates but this in December deliberately created a manual restore point incase again the update forces itself onto my system.

    AND BEHOLD yet again the update has be run even though I do not want it but at least this time my systems boot but not fully functional now with memory issues, all my start items are missing, it has corrupted my graphics drivers and at least 50% of programs will not load needing reinstall.

    With this I though hay lets just do a system restore as it will be quicker but now found the update has deleted this as well to just get a message " There were no restore points found"

    Thanks Microsoft, I spend thousands each year and you can't seem to get a simple update right.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-21T13:38:09+00:00

    Just tried to re-install graphics drivers and they still fail to load on restart. Went to go into control panel and get system call failed. Went to uninstall updates and get system call failed.

    This is turning into a nightmare, I'm surprised I can even open chrome to post

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-21T14:28:21+00:00

    After 7 or so attempts have now managed to get windows to revert to the previous build and everything works as expected.

    Please Microsoft PLEASE PLEASE PLEASE give us the option to turn the updates off. The 1709 build refuses to work on my systems and I therefore do not want it to ever install.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-22T10:06:23+00:00

    After restoring windows to an earlier time I was able to get it to boot past the windows logo. Every time windows updated to the same point it crashed. Event viewer gave me a clue as to where the problem lay, several updates. I tried to fix windows update using the trouble shooter but that did not work. To cut a long story short update KB4073290 Cumulative update solved the problem. Apparently this was all due to older AMD processors. This is a stand alone update but did not appear as a solution until I had wasted several days trying to solve the problem.

    Was this answer helpful?

    0 comments