Windows 10: Complete System Loss After Latest Tech Preview Installation

I had the exact same problem with Build 10130 (HP Elitebook 8440). After a failed upgrade with a repair-reboot-loop it was impossible to use or even reinstall any 10130 version, neither by USB nor by DVD.

I also redownloaded the version and also the x86 version to be sure that this was not a download error. I even wiped my complete harddrive without any progress. When you boot the USB stick with the iso only the windows logo will appear and then there is a reboot. And this will continue in eternity. No ISO with the build 10130 will run on my notebook.
After making sure that my harddrive was not crashed by installing Lubuntu as a test i downloaded Windows build 10049. This version installed without any problems and is now running. I have deactivated the automatic update function for as long as there is no newer build than 10130.

 

Thanks...but I can't. That's the problem.

 

Thanks very much for this. At least this gives me some idea of a way forward. I'm glad to know I'm not the only person with this problem! (Although, of course, I wish nobody had it.)

The problem now is that I cannot find a 10049 download anywhere. Do you have any idea where I can download it from? Thanks!

 

I have used this source: http://getintopc.com/softwares/opera...-bit-download/

 

Many thanks Baru. You are very kind. I shall try that. I will let you know!

Regards,

.

 

Ok, having done some reading it appears that there are a *lot* of people who've had exactly the same problem, on a wide variety of hardware platforms - everything from Surface to laptops to desktops. Microsoft are being very coy about acknowledging they have a problem with 10130 and at the moment are insisting the problem occurs due to hardware changes, in the computer it's being installed on, since the previous build, which is not the case for anybody who has replied (nor for me either). It seems that the error, in a lot of cases, corrupts the MBR record, and it occurs when the installation of 10130 commences, not at the end of the process, so some people have been able to revert to the earlier build if they've managed somehow to boot the machine (I still cannot boot mine). I have downloaded a tool which claims to fix any Win 10 installation problems or disk corruption, so I shall try that later today and report back. I've also got an ISO of an earlier build so I shall try that too.

Please also note that many people are reporting that their machines are actually stuck in a "boot loop": the machine starts, tries to execute Win 10, gets stuck on the loading screen, reboots. In my case, my machine is not rebooting but is just stuck forever on the Win 10 loading screen. Google "Windows 10 10130 boot loop" and you will see many instances of the problem being reported.

Based on all this, personally I would not recommend anybody upgrades to 10130 at the moment because there definitely seems to be a problem with it. There's no discernible pattern as to what the cause is, i.e. it doesn't appear to affect one hardware platform/config more than another, so I would suggest waiting until MS make an announcement about it and offer a fix. Which I expect them to.

Thanks for all your replies so far. They are much appreciated.

Kind regards

.

 

Right! I just re-read post# 1 *Redface

If there's no data on the drive, you can try two other paths. You might have to visit a friend or the library to build your toolbox.

Create a Linux Mint Mate flash drive : Download - Linux Mint
If this boots (it should) you can use it to copy any data first if you want.

Create a Minitool Partition Wizard Bootable CD : MiniTool Free Partition Wizard Bootable CD
You can check the drive for errors with PW - please do.

Use either to wipe the drive
Download a fresh 10.0.130 ISO and burn it to disc or make a bootable flash drive.

Install on the unallocated space - do not format the drive.

Full install instructions here: Clean install
Pay attention to the color boxes and follow any links for important information.

 

Helps *Wink.

Many thanks for all your help Slartybart. I shall try as you suggest. It now looks like I have a number of different options to try, so I shall, and report back.

Much appreciated

.

 

Yes it does help *Smile

Your welcome, sorry for the mis-directs and thanks for keeping me honest.
It's always good to have many options - good luck.

Bill
.

 

I had an issue with my system I'm not sure is OS related or not. The night after updating to build 10130, I turned my system off. When I woke the next morning attempting to boot in Windows, the system wouldn't even make it to Bios/UEFI (boot loop). After some much PIMA I narrowed it down to being unable to run more than one stick of memory (both sticks work). To solve it I ended up upgrading my MB & CPU. Probably not OS related, just seems odd for a system only 2 years old, nothing had changed (besides the OS update), on a very lite overclock (CPU only) and during a powered/powering down state. Haven't gone back to Win 10 TP since *Sad

 

It sounds very much like the same problem.

Anyway, I have now resolved the problem. I used the EasyRE Windows repair utilty (which for a limited time is FREE):

Easy Recovery Essentials | Windows Recovery and Repair CD Downloads

Not expecting any real results, I am happy to report that this great utility repaired the damage (corruption of the MBR by build 10130) and my PC is now up and running again. If you have the same problem, don't forget to stop 10130 from downloading and installing again otherwise the same thing will happen. In fact, I did this as a test, just to make sure that the error had not been caused by my machine rather than Win 10, and sure enough, when 10130 was applied to the machine the problem happened again. So I fixed it again.

When using EasyRE, when it gets to the memory test it performs, it says "Please be patient". It means it - in my case the memory test took 25 mins, and during some of that time the screen went black. So don't worry if nothing appears to happen for a while.

So, in summary, there is a major problem with Build 10130 that is affecting lots of people. Not everybody, true, and it mainly seems to be affecting Lenovo machines (so the opinion is anyway) but I certainly would not install it again.

Many thanks to everybody who has tried to help me on this thread - you have been very kind to give up your time. It is much appreciated.

I shall now mark this thread as "Solved"

Take care everybody! *Smile

.

 

I'm glad you got it sorted and thanks for marking the thread Solved.

The EasyRE Windows repair utility looks like an interesting tool - I checked out the demo video and tried to download it using the link you provided. I did not see a limited time free download though, id there a code or something else you used to get it free?

Bill
.

 

Time limited edition for 10 is at the top of the professional box but it's limited to two days.

 

Just wanted to point out that I've noticed wonky, unfixed drive behavior in Win10. Nothing reproduceable but in 9841 my NTFS external drive's MBR got curropted (thankfully was able to fix it in a chkdsk in Win.8) and in 10130, couldn't format my USB stick in FAT32....just curropted the key instead. Booted 8.1, formatted fine.

I don't know what's going on, but BACKUP DATA!