Applying 1909 Feature Update (FU) on an Laptop going into Recovery mode

Question

Hi,

We apply windows 10 1809 to 1909 FU on laptops and its keep going into recovery mode after the 1st reboot.

FU gets apply successfully but when you reboot the machine it goes into recovery mode and then you go through the steps and login back into machine again it's still on 1809, I try this on 5 laptops and it same results

FU is being installed from SCCM

1. We add a machine into a collection which runs a TS to install custom action script
2. Once TS is run then we add a machine into another collection which installs the FU
3. After installing the FU phase 1 machine gets rebooted, when the machine is rebooted in goes into recovery mode

Answer 1

It looks like BitLocker pin is being asked when the machine reboots.

It should not be asking for bitlocker pin after the first reboot as FU should be disabling this

Answer 2

Hi,

What's the system build of Windows 10 1809? Please run "winver" to check build number.

Did you make any modification on feature update?
Try to download Windows 10 1909 feature update from volume licensing service center and install it manfully on a test device to avoid feature update corruption.

Also, please check if any error message located in Event Viewer\Windows logs\System, setup?

Bests,

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

If you are deploying via MEMCM/Configmgr as you stated, then you should check the deployment status and the error message within. Some of those such as C1900 ones are driver related.

On an affected machine, go to the hidden folder C:\$WINDOWS.~BT and browse to Sources / Panther - there's log files in there which will help, especially the last dated compat_data one, as that determines which drivers are compatible and would block upgrades. The file will tell you the oemxxx.inf file and whether it's blocked. You can check that inf file, see what it is and then resolve the driver issue by an upgrade if you needed to.

Also, which is more likely because it's going into recovery mode during reboot, I would strongly recommend checking if you have any AV / security software that has system level kernel drivers which can interfere. Some versions of ForcePoint EndPoint for example had a Kernel driver which would blue screen and revert if upgrading (I saw this with 1809>1903 as well as 1809>1909) so you could test by removing the AV or security software temporarily, and attempting an upgrade again.

Answer 4

Hi,

It is just for test on a device to narrow down the issue if it caused by a corrupted feature update package, or customized part in feature update if you made.

Also to avoid Windows defender affection, we could disable it temporarily and boot computer into Clean Boot environment to install feature update on test machine. Clean boot could help us to narrow down if it caused by third party software.

As log analysis is out of forum support scope, we could create a ticket for assistance if you need to debug.

Bests,

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.