After the issues with DSIM in my prior post, this is becoming normal for Microsoft to introduce issues in each release.
I had terrible throughput via wireless. Upgraded/downgraded drivers (Intel 7265ac adapter). Tried everything. Then came across this:
Fix: Slow Wifi Issues After Installing Creators Update
Specifically, “Method 1: Disabling Receive segment coalescing (RSC) on your Wireless Adapter”. Feel free to read more here from Microsoft.
All that said, it was the root cause and disabling RSC resolved the issue.
Summarized steps (borrowing from the linked site above; refer to their site for screenshots):
- Launch an elevated Command Prompt
- Type powershell Get-Netadapter and note down the value under Name for your Wifi.
- Then type, powershell Get-NetAdapterRsc when you do this it will show you the current values, if it is False, then it is already disabled
- If it is True, then disable it by typing powershell Disable-NetAdapterRsc -Name WiFi
Replace the value for -Name with the name of your Wifi.
After being unable to install .NET 3.5 on a clean Windows 10 Pro install, this led me to do a DISM /Online /Cleanup-Image /RestoreHealth which would NOT complete.
Microsoft shipped Creators Update with missing and/or corrupt MUM files (Microsoft Update Manifest, error CBS Corrupt MUM).
Follow the guide here or here to resolve.
Basically involves removing the following Registry entries (you have to give yourself “Full Control” before you can delete them). Backup the keys just in case you ever want them.
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
Confirm in an elevated command prompt:
dism.exe /online /cleanup-image /restorehealth
I would suspect millions of Windows 10 Creators Update 64-bit machines suffer this issue and can’t properly add/remove Windows features or repair using DISM.