Windows 10 Startup Loop

specteresawy

New Member
when starting up windows it goes into batch operation then prints out error code 400d, ERR_READ_DISK_UUID and I'm stuck in this loop, tried bootrec /fixmbr, fixboot, rebuildbcd tried recovery essentials pro win 10 and hirens boot cd and windows 10 repair all failed I have access now only to command prompt and registery editor in windows repair, Is there any way to cancel or stop this batch process !!?
32349756_10157533216424768_900080825750519808_n.jpg
 

specteresawy

New Member
Can't say I've ever heard of this type of error and I've worked on Windows systems since the Win 2000
I was trying to make a new partition using a software called macrorit I applied changes and rebooted then I got this .. I don't know if it has something to do with this but I cant access the O/S the thing is I have too many applications and stuff in drive C and can't afford to lose this windows installation so I think it may be something inside O/S that does this stuff I was hoping that anybody can tell me how to stop it or maybe remove something from registry or edit in system files that can do good ... anyway thanks for your concern and response
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Altering the partition has altered the partitions unique identifier. If you have an install dvd or usb you could do a in place upgrade. Though as the windows doesn't know the UUID that could even be problematic.
 

specteresawy

New Member
Altering the partition has altered the partitions unique identifier. If you have an install dvd or usb you could do a in place upgrade. Though as the windows doesn't know the UUID that could even be problematic.
Thanks for your reply... you mean I have just to hook windows 10 usb and do upgrade if it's optional ?
 

specteresawy

New Member
Yes doing an upgrade if it's an option should save windows with the data intact
Thank you very much for your time, I'm so unlucky windows setup had compatibilty report that means I have to run install from the OS it self .. don't bother your self anymore thanks again
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
On saying that I can find nothing. You could use a Linux live DVD and external drive to grab any important data off the machine and do a reinstall and at least be back into windows. Maybe a registry search for any software keys beforehand would also be wise.
 

Antares

New Member
I just had this exact problem from another partition managing software. I did eventually find a solution after much hair pulling and digging through the registry while booted from alternate media. So, I'm leaving this for the next unlucky soul...

The software had modified HKLM\SYSTEM\ControlSet001\Control\Session Manager\BootExecute in the registry to run a program they had installed in system32.

Since I only had read only access to the registry, I renamed the offending program in system32, and then the system was able to boot. Then I was able to fix the key, which should be just "autocheck autochk *" in my case.
 
Top