the keys to ensure it does not contact MS directly for updates). In most cases these keys are made directly in the mounted install.wim so that theyĪre present before it boots for the first time (e.g. As a result of this we make some group policy settings directly in the registry. We don't join the domain during image building and so are never subject to group policy.(I've not done anything with 17763.292 yet.) So, most recently we were starting from 17763.253. We slipstream the latest SSU and cumulative into the install.wim before starting the process of building a sysprepped image from it.We build our images on hardware configured for legacy boot (this gives an image that we can use for both legacy and UEFI hardware).This isn't especially helpful, but we didn't have to do anything special to avoid bitlocker when building an image from the 17763 LTSC materials.Ī few thoughts as to what might be different:
When you boot to Safe Mode, it deactivates. Booting to Safe Mode and then rebooting normally has been confirmed by most people as a way to solve the 'Windows 10 stuck on login screen' issue. I do not enable BitLocker during the build but it appears that LTSC 2019's default is "enabled" and "awaiting activation". Sometimes, if a Windows update fails to install completely, it could cause your PC to freeze or function abnormally. I would be curious to know your results with an LTSC 2019 build.
0 kommentar(er)
