There have been a number of issues reported regarding the Microsoft Fall Creator’s Update, as known as the 1709 Update for Windows 10. These issues have been varied with the most common being BSODs of various errors.
This is not to say the update fails every time. It has installed perfectly fine for many users.
What follows is a list of known issues and possible resolutions.
- BSODs at or after install – The computer will present a BSOD after post, usually referring to a hardware issue. This is the most common issue reported and the fix may vary from computer to computer. Due to the inconsistency of errors, the errors will have to go through normal troubleshooting. Please note that sfc /scannow does not fix anything in these cases.
- Activation Issues – Windows will say that the version is not activate. If the computer is on the domain or uses a digital activation file, then this problem will self-correct eventually. If not, then manually repair the activation process.
- CPU runs high – This can appear after the update is stuck downloading or if the update is corrupt. If this happens do the following:
- Launch Command Prompt as Admin
- Run “sfc /scannow”
- Wait for the process to end and then reboot.
- Launch Command Prompt as Admin again.
- Run “Dism.exe /Online /Cleanup-image /Restorehealth”
- Check to see if the problem persists.
- Remote Desktop crashes – Reported, but not seen yet.
- Apps are missing or fail to launch – While there is no reported fix yet I believe this may be due to the user privileges. If the computer is on the domain, this problem appears to self-repair after policies are applied. Otherwise, I would suggest the steps used for the High CPU error.
At this time, we are not installing 1709 on CN computers.
If the computer is a personal computer and the customer insists on installing 1709 then please make sure to do the following:
- Ensure there is enough space one the disk and the disk is free from errors.
- Video drivers are up to date.
- Unplug all external drives and devices.
- Disable or uninstall any virus protection software.
- Perform a Windows Clean Boot.
- Use a local admin account, not a domain account.
These steps should help mitigate the risk of installing the 1709 update.