diskcryptor.org

hmm... for some reason the driver does nto laod proeprly on your system you would need to boot to a live windows and edit the registry manualyl to remove the driver

Thanks I'll check it out when I have soem spare time very busy with sandboxie right now

ich have deleted teh user and all his posts

@DmitryBritanov DC does not have device ID's as its not a driver that supports some hardware that would have an ID, its just a filter driver. What is needed is a way to break into the PE Environment started after reboot, may be one can add something to the SetupConfig.ini to first open a cmd shell b...

I haven't seen many reports of windows generally not being able to upgrade, so the issue is most likely on one way or an other DC related.
When I have some time on the weekend I'll do some experiments with upgrading in a virtual machine, lets see how that will work.

Hi,

I'll test that out, lets hope it can be easily fixed

This is not a really a safety improvements as those information can be easily faked.
If you need some additional authorization you will need some hardware token based solution.

Not yet, but it could be added, although picking a 128bit password s the safest way for the foreseeable future

I think you just need to reinstall the bootloader after the disk is restored

That is strange that should have worked