Questions about Windows Update

Recently we have received a large number of customers focusing on the following feedback to us:

1. A new computer freezes abnormally or fails to load to the next step during the first boot-up deployment activation session.

Most of these customer problems are reflected in the following two situations:

① Cannot enter the Windows desktop normally after setting up pin, and stays in the session after setting up for a long time;

② The next operation cannot be performed after networking;

③Long stagnation after logging in to the personal Microsoft account resulted in the inability to proceed to the next step;

This type of situation is common when the customer's WiFi router or network has had access to a VPN or has been used across zones, resulting in the new product not being able to connect to the Microsoft servers during the deployment session resulting in a stagnant or stuck deployment environment.

Response:

Ⅰ. Enter engineering mode to redeploy, and you cannot access any network again for a new round of deployment environment. Perform a Microsoft account login on the access network after the deployment is complete.

Ⅱ. There is a deployment environment machine stuck or frozen, the probability of this situation is that the deployment environment has a patch package auto-installation resulting in stuck. The situation can try to wait for a period of time to check whether it will continue to run, if it can not run. It is recommended to reinstall the outgoing image package;

Operational Guidance Document:

2. Some users in the case of unknowingly Windows completed an automatic update and an update reboot led to the computer can connect to the network, but can not use the Internet, the product WiFi, wired network are realistic and normal connection, the computer comes with the network judgment is also shown as normal, the situation is because of the Windows patch package KB5044285 and KB5044033.

These two patch packs probabilistically cause all ingress traffic to be restricted, and the default profile does not match what it should, resulting in an inability to use the network properly.

 Measures to address:

Click Windows, click Windows Settings, click "Network and Internet", click "Proxy", select all three options: "Automatically detect settings", "Use setup scripts" and "Manually turn on proxy server", then you can access the network normally. "Use Setup Script", "Manually open the proxy server" three options all choose to close, you can access the network normally, if the customer has the requirements of the three categories, can only go back to the original version of the deployment in accordance with the parameters of the proxy again.

3. Some customers are experiencing triggered  BitLocker Recovery situation:

This scenario is commonly caused by customers inadvertently triggering Microsoft's system protection mechanisms resulting in the triggering of the  BitLocker Recovery In this case, you need to go to Microsoft's official website to retrieve the 48-digit password, please refer to Microsoft's official operation guide for details:

BitLocker Overview - Microsoft Support

Failure to retrieve the password will result in the data on the hard disk being completely formatted or locked up making it impossible to use any of the data, resulting in the loss of data!

4. After updating 24H2, customers are unable to use the external camera in the software.

This type of situation belongs to the 24H2 self-contained bugs, back to the system can be.

References Windows 11 Version 24H2 Known Issues and Notifications | Microsoft Learn

5. After the Windows update (KB5043145), some customers reported multiple device reboots or blue or green screens.  screen or green screen is not responding. It is recommended to refresh the outgoing system.

Reference: Windows 11 Version 23H2 Known Issues and Notifications | Microsoft Learn