Win10 don't boot after installation

A

Akashic

New member
Hi,

After installing Build v1.2 Beta 3 on Windows 10 and restarting machine on prompt, system doesn't boot anymore - just blue screen without any error code.
I'm trying to restore the boot partition using various tutorials but so far no luck (bootrec finds no windows installations). Any tips?

Regards,
a.
 
Yes!

Use the tool https://rufus.ie/de/ and an external USB HDD to create a live windows 10 disk,
boot form it, finish the win 10 setup on that disk,
once on the desktop, install DiskCryptor and reboot.
After the reboot you can use DC from the live insolation to mount the built in encrypted drives, decrypt them, uninstall or reinstall the boot loader and etc...

Cheers
David X.
 
DavidXanatos said:
Yes!

Use the tool https://rufus.ie/de/ and an external USB HDD to create a live windows 10 disk,
boot form it, finish the win 10 setup on that disk,
once on the desktop, install DiskCryptor and reboot.
After the reboot you can use DC from the live insolation to mount the built in encrypted drives, decrypt them, uninstall or reinstall the boot loader and etc...

Cheers
David X.
Click to expand...
hey so I have the same issue with the same v1.2 beta 3. The affected original OS drive will not show up on windows live or diskcryptor or diskmanager. Tried swapping slot with another drive as well. The drive is a pcie m.2 samsung MZ-VLB512B
 
DavidXanatos said:
Yes!

Use the tool https://rufus.ie/de/ and an external USB HDD to create a live windows 10 disk,
boot form it, finish the win 10 setup on that disk,
once on the desktop, install DiskCryptor and reboot.
After the reboot you can use DC from the live insolation to mount the built in encrypted drives, decrypt them, uninstall or reinstall the boot loader and etc...

Cheers
David X.
Click to expand...
hey so I have the same issue with the same v1.2 beta 3. The affected original OS drive will not show up on windows live or diskcryptor or diskmanager. Tried swapping slot with another drive as well. The drive is a pcie m.2 samsung MZ-VLB512B
 
DC does not do anything that could damage a drive, aside of putting it under a lot of load while en/de-crypting, so a close to death drive can be pushed past the threshold.
try it in an other pc for good measure a OEM diaglosis tool if available
 
DavidXanatos said:
DC does not do anything that could damage a drive, aside of putting it under a lot of load while en/de-crypting, so a close to death drive can be pushed past the threshold.
try it in an other pc for good measure a OEM diaglosis tool if available
Click to expand...
im not so sure this drive was at all close to death. maybe a little short on free space but I bought it only about three years ago. just for clarity, I did not run diskcryptor at all and certainly didn't try to encrypt my system drive (the affected drive). all I did was run the installation and manually restarted the computer when I reached the end (in other words, i would "restart later" and then closed out/saved everything before restarting). this is precisely when the error started.

The only other nonapple laptop that I have does not have a slot for a pcie ssd. I have a usb type c dongle that I connect to the working laptop, but the drive will still not show up for me to scan it. both laptops are lenovo thinkpads running windows 10. I'll try to connect that to the working laptop and run diagnostic tools. praying I haven't lost my data
 
DavidXanatos said:
DC does not do anything that could damage a drive, aside of putting it under a lot of load while en/de-crypting, so a close to death drive can be pushed past the threshold.
try it in an other pc for good measure a OEM diaglosis tool if available
Click to expand...
So what everyone seems to think is that the drive was automatically encrypted by the program. I'm in pretty desperate straits as none of that data was backed up and so much completed work from my recently finished undergrad were all on that drive. I had a nearly finished scientific paper I was hoping to get published which may be lost :(

Do you have any other ideas? Even if it WAS encrypted, I never put in a password or even ordered its execution so I am not sure how I might decrypt it.
 
I had the same problem. For me, what fixed it was

Advanced startup options - Troubleshoot - Advanced options - Startup settings - Restart - Disable driver signature enforcement.

this only lasted for one boot. The problem came back every boot until I uninstalled the software.

Do I need to disable it forever? I have installed the same copy of the same EXE on two other computers without an issue.

I think this should be prominently explained when you install.
 
The 1.2.3 build had signature issues in certain configurations.
the recently released 1.3.0 is signed the newest MSFT prescribed way and should not have any issues with driver signature.
 
You must log in or register to reply here.
Back
Top