December 10, 20196 yr Author Then I guess Ctrl+Shift+ESC also don't work. Try to boot in safe mode. It could be a problem with fastboot or drive letter assignment.
December 10, 20196 yr Booting in Safe Mode is working OK. After safe Mode then normal booting is working OK Edited March 27, 20242 yr by wimb
December 11, 20196 yr 18 hours ago, wimb said: Booting in Safe Mode is working OK. After safe Mode then normal booting is working OK I have done a lot of testing now on what is causing the logon failure after Apply of Updated Windows 10 x64 Version 1909 on internal GPT SSD booting in UEFI Secure Mode. I can conclude now that this behaviour is not affected by Disable Hibernate Or BootMenuPolicy (Legacy / Standard) Or Local Account instead of Microsoft Account Or wimlib instead of WimGAPI. It turns out that just Windows Update of the fresh installed Windows 10 x64 1909 is causing this logon failure After Apply of a Captured WIM file of this Updated 1909 Windows x64 version. This Windows Update involves Windows explorer.exe to change from version 10.0.18362.387 into 10.0.18362.449 Strange enough first booting into Safe Mode solves the problem. Probably the Microsoft Security is too Severe ...... Edited December 11, 20196 yr by wimb
December 11, 20196 yr Author Safe mode only loads basic stuff. It properly marks something in registry as done. And next full start will work (we have seen similar in WinPE) One thing would be interesting: Is there a difference using VSS or offline capture?
December 11, 20196 yr @wimb Perhaps a second reboot after applying the update, before capture could solve the issue too. And then no need to boot in Safe Mode after applying the image. alacran
December 11, 20196 yr JFYI In some cases it is good to control the expansion of an expandable VHD, a simple reg file added by means of WinNTSetup >>> Tricks, will do it. For more info see: http://reboot.pro/topic/22195-vhd-virtual-disks-tips-and-tricks/#entry213553 alacran Controlled-Expansion-VHD.reg Edited December 11, 20196 yr by alacran Typo
December 12, 20196 yr 18 hours ago, JFX said: One thing would be interesting: Is there a difference using VSS or offline capture? The logon failure for Applied Updated 1909 Win10x64 is sometimes solved by using VSS offline Capture, but it is not a reliable solution for the problem. @alacran After Windows Update I always reboot more times to be sure before Capture, but that did not solve the logon failure on Apply.
December 12, 20196 yr Author @alacran This tweak was already added with RC2 under the following condition. Free space is smaller than max vhd expanded size - 5%. Without disabled pagefile additional 6GB free space are expected.
December 12, 20196 yr @JFX Sorry I didn't know it is already applied on WinNTSetup. @wimb It was only an idea trying to avoid the need to boot in Safe Mode, and yes it is a good practice the way you do it. Edited December 12, 20196 yr by alacran
December 14, 20196 yr On 12/11/2019 at 4:12 PM, JFX said: One thing would be interesting: Is there a difference using VSS or offline capture? For the case of Win10x64 1909 Updated to version 10.0.18362.535 Online VSS Capture using WimGAPI + Defender Off is working very fast and After Apply is OK for logon. WIM File of Size 6.05 GB is Captured with Defender Off in less than 2 min (1:55 min) and with Defender On in 14 min Edited December 14, 20196 yr by wimb
December 14, 20196 yr 10 hours ago, wimb said: For the case of Win10x64 1909 Updated to version 10.0.18362.535 Online VSS Capture using WimGAPI + Defender Off is working very fast and After Apply is OK for logon. WIM File of Size 6.05 GB is Captured with Defender Off in less than 2 min (1:55 min) and with Defender On in 14 min Please share this tools
December 14, 20196 yr 10 minutes ago, AshtonLee.IT said: Please share this tools It is WinNTSetup Download Current Version 4.0, which has Local Windows Installations as Menu item available to Capture Wim .... Edited December 14, 20196 yr by wimb
December 14, 20196 yr 3 minutes ago, wimb said: It is WinNTSetup Download Current Version 4.0, which has Local Windows Installations as Menu item available to Capture Wim .... OK Hirren option
December 15, 20196 yr Author @AshtonLee.IT We had discussion about the version of BOOTICE, see here. On 12/14/2019 at 8:22 AM, wimb said: For the case of Win10x64 1909 Updated to version 10.0.18362.535 Online VSS Capture using WimGAPI + Defender Off is working very fast and After Apply is OK for logon. WIM File of Size 6.05 GB is Captured with Defender Off in less than 2 min (1:55 min) and with Defender On in 14 min Glad it works now. This slow down with Defender is a bit extreme. But i guess an option to disable realtime monitoring during capture would properly cause one more false positive.
Create an account or sign in to comment