Microsoft Bricked my windows...

[TheNuzziNuzz]

Last night I fell asleep to windows 10 downloading updates. When I woke up to get to work on my computer, which is where I do all my business, I was greeted by a boot loop. What a wonderful way to start a day!

 

It starts on the normal spiral loading, then changes to say "Loading System Recover" for a about a second, then switches to "Rolling back windows updates" then restarts and does it again. As you can imagine this is very frustrating. So I got my windows 10 recovery drive, and it does the same thing. I disconnected my main drive, then the recovery booted, reconnected and starting the fixing.

 

Under "Go back to the previous version" I get "We ran into a problem and wont be able to take you back to the previous version. Try resting this PC"

Startup repair cant fix it, and it can't find any backups/recovery images even though I know I have them.

 

The drive windows is installed on has all my work files, don't worry they are backed up. BUT, this is freaking insane because now I cannot do my JOB until I reinstall windows, restore my backup, install all my programs again for work, and OMFG this was all Microsoft fault.

 

 

If anyone else has any ideas to possibly salvage any of my day, or files, back that would be awesome. And I also wan't to just shed some light on how frustrating windows 10 forced updates can be. I'm considering taking legal action, what do you guys think?

 

Thanks!

[79wjd]

4 minutes ago, TheNuzziNuzz said:

I'm considering taking legal action, what do you guys think?

Literally nothing will ever come of it, so don't waste your time. 

 

If it's really a concern going forwards, then A) you can delay updates up to 90 days I think, and B) create a mirror'd boot drive for just in case moments.

[TheNuzziNuzz]

Just now, djdwosk97 said:

Literally nothing will ever come of it, so don't waste your time. 

 

If it's really a concern going forwards, then A) you can delay updates up to 90 days I think, and B) create a mirror'd boot drive for just in case moments.

I'm on my way to bestbuy to buy a new SSD haha. I had actually delayed it over a year, I'm still on one of the first version of windows 10. Thats probably part of the reason it did't work. But good to raise awareness here on the forums anyway.

[Ace McPlane]

6 minutes ago, TheNuzziNuzz said:

Last night I fell asleep to windows 10 downloading updates. When I woke up to get to work on my computer, which is where I do all my business, I was greeted by a boot loop. What a wonderful way to start a day!

 

It starts on the normal spiral loading, then changes to say "Loading System Recover" for a about a second, then switches to "Rolling back windows updates" then restarts and does it again. As you can imagine this is very frustrating. So I got my windows 10 recovery drive, and it does the same thing. I disconnected my main drive, then the recovery booted, reconnected and starting the fixing.

 

Under "Go back to the previous version" I get "We ran into a problem and wont be able to take you back to the previous version. Try resting this PC"

Startup repair cant fix it, and it can't find any backups/recovery images even though I know I have them.

 

The drive windows is installed on has all my work files, don't worry they are backed up. BUT, this is freaking insane because now I cannot do my JOB until I reinstall windows, restore my backup, install all my programs again for work, and OMFG this was all Microsoft fault.

 

 

If anyone else has any ideas to possibly salvage any of my day, or files, back that would be awesome. And I also wan't to just shed some light on how frustrating windows 10 forced updates can be. I'm considering taking legal action, what do you guys think?

 

Thanks!

Yea, don't bother taking legal action.

Microsoft can afford better lawyers than you can

In all seriousness, if people could sue over that, they would have been doing it a long time ago.

 

Sadly, it sounds to me like you've exhausted all of your avenues besides reinstalling windows.

 

[NMS]

Legal action? You will only suffer more.

 

In my opinion, something definitely happened during the Windows installation (power outage, disk failiure, ...), but unfortunately you were not "there" to witness it.

Could you pick a fresh install of Windows from the website and try to roll back the changes from that drive? I think there's an option to remove the latest update using recovery menu. Yes you tried that, but it won't hurt to do it again with a newest version.

[TheNuzziNuzz]

1 minute ago, NMS said:

Legal action? You will only suffer more.

 

In my opinion, something definitely happened during the Windows installation (power outage, disk failiure, ...), but unfortunately you were not "there" to witness it.

Could you pick a fresh install of Windows from the website and try to roll back the changes from that drive? I think there's an option to remove the latest update using recovery menu.

Yes I did that, The recovery/rollback failed

[NMS]

4 minutes ago, TheNuzziNuzz said:

Yes I did that, The recovery/rollback failed

Sounds like corrupted windows files. Good luck with the new installation!

[NinJake]

Rather than get angry at Windows about the whole situation, take it as a learning experience and create a plan of attack to make sure this doesn't happen to you so drastically again. While you may not be able to control "Windows bricking your computer", you do have control over where your software and work files are saved.

[tyepow]

If your computer is required for your work, why don't you protect it better?

A secondary drive, an OS that doesn't fubar itself overnight, IT support contractor...

I mean, I know people get upset when things fail, but things are known to almost certainly fail at some point. If it's mission critical, have a backup plan.

[Enderman]

Usually this only happens if you did something wrong, such as upgrade to windows 10 without clean installing, cloning a drive, making registry edits, etc.

[NinJake]

Just now, Enderman said:

Usually this only happens if you did something wrong, such as upgrade to windows 10 without clean installing, cloning a drive, making registry edits, etc.

Can confirm. Set up 4 personal windows 10 PC's, and 20+ at work and so far none have gone FUBAR.

[ARikozuM]

You should have images of the OS made on a meaningful basis (say weekly or daily). 

 

Edit: You may be able to use a Windows 10 disc or USB to use startup repair from there rather than the disk.

[Zando_]

1. macOS is better, breaks itself a lot less 

2. Installing windows looks like the best option. What are your files backed up to? If it's the cloud, you'll want to boot into linux or something off a USB and copy them to an external HDD so you can get them back faster. 

[79wjd]

 

8 hours ago, Zando Bob said:

1. macOS is better, breaks itself a lot less 

It doesn't break itself, but god help you if you have to run Outlook.

[Skyyblaze]

9 hours ago, Enderman said:

Usually this only happens if you did something wrong, such as upgrade to windows 10 without clean installing, cloning a drive, making registry edits, etc.

I really want to say unless you did some heavy "modding" having to clean-install Windows 10 especially is a myth. I haven't clean installed any Windows since I first installed Windows 7 64bit and I never ran into issues. Besides upgrading between Windows versions is a endorsed feature.

[79wjd]

5 minutes ago, Skyyblaze said:

I really want to say unless you did some heavy "modding" having to clean-install Windows 10 especially is a myth. I haven't clean installed any Windows since I first installed Windows 7 64bit and I never ran into issues. Besides upgrading between Windows versions is a endorsed feature.

It's an endorsed feature -- so I wouldn't say that "upgrading" is wrong, but it is still very prone to problems. It seems like there are far more issues with systems running on an upgraded OS than those that are running on a clean install -- and it makes perfect sense that that's the case.

[Skyyblaze]

Just now, djdwosk97 said:

It's an endorsed feature -- so I wouldn't say that "upgrading" is wrong, but it is still very prone to problems. It seems like there are far more issues with systems running on an upgraded OS than those that are running on a clean install -- and it makes perfect sense that that's the case.

I don't even disagree here but atleast Windows 10 seems to be far more upgrade proof than previous versions. I never thought I would say that but in the grand scheme of things the majority of Windows 10 upgrades work fine from what I saw. Of course there are still big messes here and there but generally it seems to work. I actually would like to see a Workshop episode on this along with "Do you really have to clean-install Windows when changing hardware?"