Laptop dead after 1709 upgrade

I have had to avoid deploying 1709 mainly due to the fact that it was bricking all physical devices HP 725/745/612/X360 and rendering them dead halfway through the upgrade with no ability to rollback. This was back in October when we started to test this and the only virtual machines could be upgraded.

It was only recently that I found an article pointing a finger at a new setting in the latest baselines

https://blogs.technet.microsoft.com/secguide/2018/01/18/issue-with-bitlockerdma-setting-in-windows-10-fall-creators-update-v1709/

After changing this to “disabled” upgrades to 1709 now work.

More info here

https://support.microsoft.com/en-gb/help/4057300/devices-not-working-before-log-on-a-computer-running-windows-10-1709

Baselines modified for RS2/RS3 as below.

MSFT Windows 10 RS2 – Computer

Computer Configuration | Policies | Administrative Templates | Windows Components | BitLocker Drive Encryption = Disabled

MSFT Windows 10 RS3 – BitLocker

Computer Configuration | Policies | Administrative Templates | Windows Components | BitLocker Drive Encryption = Disabled

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s