Open th-wilde opened 7 years ago
Patch initially created and working to Upgrade a Fujitsu Lifebook E754 in BIOS-Mode with "entire system drive"-Encryption.
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1607 Upgrade to Version: 1703 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.19
Successfully tested a (U)EFI-Setup with an VirtualBox-VM with "windows partition"-Encryption.
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: (U)EFI Encryption-Mode: windows partition Upgrade from Version: 1607 Upgrade to Version: 1703 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.19
Follow up Upgrade of the Fujitsu Lifebook E754 (mentioned in my first comment). Successfully Upgraded to "Fall Creators Update" (1709)
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.21
Tested on an HP Envy Core i7 / UEFI mode / non secure boot. There was an issue initially with this UEFI firmware, i had to manually start Veracrypt bootloader. In the end, i disabled Windows boot manager (changing order was not working, WBM always comes first again after the next reboot). I did the change with EasyUEFI. When i started the update, i left things as-is. At 2nd stage install, the veracrypt bootloader started, then, it continues. It needed 3 reboots to complete the full upgrade.
Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: iso download with media creation tool, unzipped on my hard drive, then patched with your tool Installed VeraCrypt-Version: 1.21
Upgrade of the HP 15 TS Notebook. Successfully Upgraded to "Fall Creators Update" (1709)
Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: ISO download with media creation tool, unzipped on my hard drive, then patched with your tool Installed VeraCrypt-Version: 1.21
This process worked like a champ! Thanks so much.
Upgrade to W10 Fall Creator Update
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: media creation tool with an ISO image Installed VeraCrypt-Version: 1.21
At first it failed because I created a bootting USB drive with Media Creation Tool, then I found you said it must be an ISO image. You should put that information in the README, so everyone will know it.
You could also say that it take almost 2 hours to patch the W10 installation files.
Thanks a lot for this very useful tool !!!
I upgraded another computer to W10 Fall Creator Update
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 10240 (a very old W10 installation) Upgrade to Version: 1709 Media used to Upgrade: media creation tool with an ISO image Installed VeraCrypt-Version: 1.21
Thanks a lot for this very useful tool !!!
Hi,
I upgraded a laptop encrypted with TrueCrypt to Windows 10 1709 (Build 16299.125). I just had to replace "VeraCrypt" with "TrueCrypt" in relevant places (and watch out the capitalization) and it worked as I had assumed. (If you want I can send you the updated script or create a pull request, although probably anyone can do it. Maybe you can add a truecrypt-w10-patcher.cmd file.)
Windows Edition: Education Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed TrueCrypt-Version: 7.1a
Here my configuration: Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: windows partition Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.19
First, the words "Profound Thanks!!!" do not begin to express my emotions right now. I've struggled with this issue for months now. th-wilde, you've really done an outstanding service. Thank you.
At first, I had media creator tool install on a USB drive. I followed the instructions and this failed. It gave the error, "0xC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation."
So finally, I copied the Windows.iso files onto an unencrypted partition on the same drive as my C drive. Followed the instructions from here and it work with no issues.
Comments: I finally read in someone's comments that this wouldn't work from a USB drive, but I couldn't see that clearly in the instructions. If this is the case, it would be better to show it clearly. Also, the script deletes the file "install.esd". I don't think this is necessary. The reason that I mention it is that I screwed up the first time and ended up have to download the install tool twice. Several GBs of wasted time and bandwidth. (I hate to think of how many times I have downloaded the updates files over the previous months!) Edit: Still working with the 2018 Fall update.
Worked perfectly! Huge kudos to you!
I'm so happy you made this because I've been holding off upgrading Windows for a long time, since I really didn't want to decrypt and then re-encrypt the entire system (partially because of the wear it would have caused on my ssd). This saved me from switching to BitLocker!
I did experience an initial problem though, because of the instruction to "Place the script into the root of a Windows 10 installation media". To me, this means that I'm supposed to "burn" the iso to an usb drive (a physical installation media) and then place the script in the root of that usb drive. That's what I did, and because the script mentions that there will be error messages but they can be ignored, I naturally though the error message I got could be ignored. Luckily I then verified if veracrypt.sys had really been patched into the images in the wim before I tried running setup.exe, and found that this had not been done. I then watched your YouTube video and finally understood what I actually had to do; copy the contents of the iso into a folder on my ssd and run the script there. I think it would be a good idea to be very specific about this in the instructions. :)
If I hadn't verified that veracrypt.sys was actually patched in, the upgrade would have failed. I wonder if this has happened to others?
Windows Edition: Pro Architecture: 64Bit Firmeware-Mode: BIOS ((U)EFI in CSM mode) Encryption-Mode: Entire system drive Upgrade from Version: 1511 Upgrade to Version: 1709 Media used to Upgrade: MediaCreationTool Installed VeraCrypt-Version: 1.21
Update from 1607 also works, thx for the script!
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1607 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.17
Worked!
Windows Edition: Pro Architecture: 64bit Firmeware/-Mode: UEFI Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.21
Thanks for the script!
I made a video walk through with commentary:
After many SAFE_OS errors I finally managed to do upgrade. I wonder did downloading "64bit only ISO" helped me. Note that Rufus tries format USB-stick as FAT32 for UEFI GPT system by default, so script will fail since final install.wim will be around 7GB. But otherwise upgrade worked fine form USB-stick.
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: Entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: Media creation tool Installed VeraCrypt-Version: 1.21
Worked(in general), but not perfect: #12 Windows Edition: Education Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: Entire system drive Upgrade from Version: 1607 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.21
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.21
The first time I tried to do it, something went wrong so I accidentally installed the updates from Windows Update. The second time around I quickly installed the already prepared updates with the VeraCrypt patch and everything went fine. However: For some reason VeraCrypt now won't automatically mount my other encrypted drive, I have to manually mount it and enter the password when I'm logged-in to Windows. Any ideas why this happened?
Worked like a charm
Here my configuration: Windows Edition: [Pro ,Home, Education, Enterprise, ...] Architecture: 64Bit Firmeware/-Mode: UEFI no CSM Encryption-Mode: windows partition (other partition contains Ubuntu 17.10 with EcryptFS) Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: Torrent ISO 1803 RTM Installed VeraCrypt-Version: 1.21
Worked! Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: windows partition Upgrade from Version: 1607 Upgrade to Version: 1709 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.19
Another successful run Windows Edition: Pro Architecture: 64bit Firmeware/-Mode: UEFI Encryption-Mode: Entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: Media Creation Tool Installed VeraCrypt-Version: 1.21
Worked perfectly
Here my configuration: Windows Edition: Home China Architecture: 64Bit Firmeware/-Mode: (U)EFI Encryption-Mode: windows partition Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: 1803 ISO from microsoft Installed VeraCrypt-Version: 1.22
Nice! It worked for me. I noticed ....... no problem whatsoever. Thank you!
Here my configuration:
Windows Edition: Pro
Architecture: 64Bit
Firmeware/-Mode: legacy
Encryption-Mode: windows partition
Upgrade from Version: 1709
Upgrade to Version: 1803
Media used to Upgrade: MediaCreationTool1803.exe
-> ISO, extracted, added and ran script (took about two hours), then ran setup and it restarted ~5 times
Installed VeraCrypt-Version: 1.22
Worked for me for 1803. Very nice :)
Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: whole system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: MediaCreationTool1803.exe -> ISO, extracted, added and ran script Installed VeraCrypt-Version: 1.21
Worked great updating to 1803
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: (U)EFI Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: Win10_1803_English_x64.iso from Microsoft Installed VeraCrypt-Version: 1.22
Updated to 1803. Thank you! Taking crypto or paypal donations?
Here my configuration: Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: (U)EFI Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: Media Creation Tool, ISO (extracted) Installed VeraCrypt-Version: 1.22
Macbook Pro standalone Windows 10 user here (No OSX, No bootcamp, Only Windows, BIOS mode - Legacy)
Updated to 1803 successfully.
Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: media creation tool, ISO (extracted) Installed VeraCrypt-Version: 1.22
Upgrade of a Fujitsu Lifebook E754: A little bit special, because I skip 1709 on this machine. It goes from 1703 straight to 1803 without any problems.
Here my configuration: Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: BIOS (UEFI with CSM) Encryption-Mode: entire system drive Upgrade from Version: 1703 Upgrade to Version: 1803 Media used to Upgrade: media creation tool (ISO) Installed VeraCrypt-Version: 1.22
Windows Edition: Education Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: media creation tool Installed TrueCrypt-Version: 7.1a
Lenovo V110 Laptop; Windows 1709 --> 1803
Nice! It worked for me. But it took a couple of attempts before I noticed that, after the initial installer reboot, the VeraCrypt boot option in EFI was getting erased. The solution was to reinstall it using the VeraCrypt Rescue Disk, but in the end it worked. The recipe for my success is below. YMMV.
Here my configuration:
I used the following method:
I second @EventuallyFixed thx! I did one up by using the "VeraCrypt Recovery Disk" usb stuff from here - http://sourceforge.net/projects/veracrypt/files/Contributions/VeraCryptUsbRescueDisk.zip/download
yet the Recovery was not needed in the end
Wow, holy moly I had been struggling to figure out why my 1803 updates kept failing. I never even thought about VeraCrypt. While it took DISM forever to do its thing, the script worked perfectly! Much love! <3
This was done on a custom built system with an ASRock mobo.
Parameters: Windows Edition: Windows 10 Pro Architecture: 64 bit Firmeware/-Mode: (U)EFI Encryption-Mode: Entire system drive Upgrade from Version: 1703 Upgrade to Version: 1803 Media used to Upgrade: Media creation tool Installed VeraCrypt-Version: 1.21
Nice! It worked for me. <3
But i have a probleme with my second disk (i can mount it without password)
link : https://youtu.be/h4w7OXZ07cA
Windows Edition: Enterprise Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1607 Upgrade to Version: 1803 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.22
Windows Edition: Home Architecture: 64Bit Firmware/-Mode: UEFI Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.21
Used a Win 10 ISO downloaded recently via media creation tool. Extracted the ISO with 7zip to a folder on the encrypted drive (C:\ISO\ etc) 7Zip threw an error to the effect that "There are some data after the end of the payload data" - but it was fine to proceed anyway in this case Ran the patcher and let it do its thing for a good long while Ran the update from within Windows Success
Initial RTFM fails included trying this off a USB pen and using the downloaded media creation files rather than downloading an ISO and extracting it.
Many thanks to th-wilde for this resource, and all users for their comments.
Upgrade of the HP 15 TS Notebook. Successfully Upgraded to (1803).
Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1803 Media used to Upgrade: ISO download with media creation tool, unzipped on my hard drive, then patched with your tool Installed VeraCrypt-Version: 1.21
This process worked like a champ! Thanks so much.
Lenovo laptop, first patched update 1709->1803, then today 1803->1809 So now I combine Windows bloatware with the hassle of a linux-like update process, hooray!
Parameters: Windows Edition: Windows 10 Pro Architecture: 64 bit Firmeware/-Mode: BIOS Encryption-Mode: Entire system drive Upgrade from Version: 1803 Upgrade to Version: 1809 Media used to Upgrade: Media creation tool Installed VeraCrypt-Version: 1.21
Parameters: Windows Edition: Windows 10 Pro Architecture: 64 bit Firmeware/-Mode: (U)EFI Encryption-Mode: Entire system drive Upgrade from Version: 1803 Upgrade to Version: 1809 Media used to Upgrade: Media creation tool Installed VeraCrypt-Version: 1.22
Note that among the update restarts the VeraCrypt bootloader entry got overwritten, resulting in a bootloop. I had to boot to the install media, open up the console and revert the entry:
bcdedit /set {bootmgr} path \EFI\VERACRYPT\DCSBOOT.EFI
After that everything worked.
Parameters: Windows Edition: Windows 10 Pro Architecture: 64 bit Firmeware/-Mode: BIOS Encryption-Mode: Entire system drive Upgrade from Version: 1803 Upgrade to Version: 1809 Media used to Upgrade: Media creation tool Installed VeraCrypt-Version: 1.22
Updated with no problems.
Extracted the ISO using WinRar, and ran the script.
I did NOT reboot to execute the bcdedit command, since my boot option was never removed.
After that I simply ran setup.exe and selected Windows 10 Enterprise N LTSC 2019
, waited for about 20 minutes and it was done.
Configuration: Laptop: ASUS ROG Strix GL703GS Previous Windows Edition: Enterprise N LTSB 2016 Upgraded Windows Edition: Enterprise N LTSC 2019 Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: windows partition Upgrade from Version: 1607 Upgrade to Version: 1809 Media used to Upgrade: en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.iso Installed VeraCrypt-Version: 1.22
Upgrade of the HP 15 TS Notebook. Successfully Upgraded to (1809).
Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: entire system drive Upgrade from Version: 1803 Upgrade to Version: 1809 Media used to Upgrade: ISO download with media creation tool, unzipped on my hard drive, then patched with your tool Installed VeraCrypt-Version: 1.23-Hotfix-2 (64-bit) -- note I upgraded this first from 1.21 to this 1.23+. Then I followed the above process.
This process worked like a champ! Thanks so much.
Worked for me without a hitch.
Here's my configuration: Upgrade Method: ReflectDrivers Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: entire system drive Upgrade from Version: 1709 Upgrade to Version: 1809 Media used to Upgrade: media creation tool, made ISO, extracted to unencrypted drive Installed VeraCrypt-Version: 1.23-Hotfix-2
On Truecrypt. Failed with ReflectDrivers, success with MediaPatcher
Here my configuration: Upgrade Method: [MediaPatcher] Windows Edition: [Pro] Architecture: [64Bit] Firmeware/-Mode: [BIOS] Encryption-Mode: [entire system drive] Upgrade from Version: [1809] Upgrade to Version: [1903] Media used to Upgrade: [media creation tool, files copied to another (encrypted) hd] Installed VeraCrypt-Version: [TrueCrypt 7.1a]
Nice! It worked for me. I noticed 3 restarts but in the end it worked.
Here my configuration: Upgrade Method: [ReflectDrivers] Windows Edition: [Pro] Architecture: [64Bit] Firmeware/-Mode: [UEFI] Encryption-Mode: [entire system drive] Upgrade from Version: [1903] Upgrade to Version: [1909] Media used to Upgrade: [TechBench by WZT] Installed VeraCrypt-Version: [1.24 Hotfix1]
It worked flawlessly for me. Stupid me didn't read instructions originally and I didn't add /ReflectDrivers
manually, but the second attempt was successful.
Here's my configuration: Upgrade Method: ReflectDrivers Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: Windows partition Upgrade from Version: 1909 Upgrade to Version: 2004 Media used to Upgrade: Official ISO download, media created with Rufus Installed VeraCrypt-Version: 1.24-Update6
HP Envy Core i7 / UEFI mode / non secure boot.
Upgrade Method: ReflectDrivers Windows Edition: Home Architecture: 64Bit Firmeware/-Mode: UEFI Encryption-Mode: entire system drive Upgrade from Version: 1909 Upgrade to Version: 2004 Media used to Upgrade: Official ISO download, unzipped locally Installed VeraCrypt-Version: 1.24-Update6
Worked perfectly
Upgrade Method: ReflectDrivers Windows Edition: Education Architecture: 64Bit Firmeware/-Mode: BIOS Encryption-Mode: Entire system drive Upgrade from Version: 1709 Upgrade to Version: 1909 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.24-Update6
Worked perfectly! Thanks! (Why did it take me until now to find this? Finally no more decrypt/encrypt..)
Upgrade Method: ReflectDrivers Windows Edition: Home Architecture: 64Bit Firmware/-Mode: UEFI Encryption-Mode: Entire system drive Upgrade from Version: 1909 Upgrade to Version: 2004 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.23-Hotfix2
Worked on the first try, now running 20H2 👍
Here's my configuration: Upgrade Method: ReflectDrivers Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: tbh I don't really know Encryption-Mode: entire system drive Upgrade from Version: 1909 Upgrade to Version: 20H2 Media used to Upgrade: media creation tool, ISO unpacked on C:\ with 7Zip Installed VeraCrypt-Version: 1.24-Update7
Worked on the first try, now running 20H2 👍
For 20H2, you don't need the patch nor you need to install from media. The in-place upgrade through Windows Update works on encrypted disks (at least it did in the 5 computers I updated).
Worked on the first try, now running 20H2 👍
For 20H2, you don't need the patch nor you need to install from media. The in-place upgrade through Windows Update works on encrypted disks (at least it did in the 5 computers I updated).
Well damn, I sure wish I would have known that 48 hours earlier.
Worked on the first try, now running 20H2 👍
For 20H2, you don't need the patch nor you need to install from media. The in-place upgrade through Windows Update works on encrypted disks (at least it did in the 5 computers I updated).
Can someone else confirm? This is huge
Worked on the first try, now running 20H2 👍
For 20H2, you don't need the patch nor you need to install from media. The in-place upgrade through Windows Update works on encrypted disks (at least it did in the 5 computers I updated).
Can someone else confirm? This is huge
Yes, check the front page for more information: https://github.com/th-wilde/veracrypt-w10-patcher#upgrading-with-the-reflectdrivers-mechanism
This has worked since Win 10 1607, and doesn't have anything to do with 20H2.
The manual command line option is probably still required when installing from media, however.
Works, thanks! My configuration:
Upgrade Method: ReflectDrivers Windows Edition: Pro Architecture: 64Bit Firmeware/-Mode: UEFI (but I'm not sure) Encryption-Mode: entire system drive Upgrade from Version: 2004 Upgrade to Version: 20H2 Media used to Upgrade: media creation tool Installed VeraCrypt-Version: 1.24-Update6
Hello, this issue is created to track configurations in witch a upgrade works. If the upgrade worked for you, please share your success here with some details. If the upgrade failed please report your disappointment in the "Hall of Blame"-Issue (#3).
Please use the following template for your comment to keep some structure. If you do not know some of the requested details, just let them empty.