3 ms·
Wait what? This cannot be serious.
by NullPrefix 7y ago
Wait what? This cannot be serious.
- wtallis 7y agoApparently Microsoft did get a fix out earlier this week; I'd been avoiding my Windows machines waiting for this. The patch that introduced the bug: https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941 https://support.microsoft.com/en-us/help/4512941/windows-10-... The patch that fixed the bug: https://support.microsoft.com/en-us/help/4515384/windows-10-update-kb4515384 https://support.microsoft.com/en-us/help/4515384/windows-10-... Description and workaround: https://www.reddit.com/r/Windows10/comments/cxmot9/windows_10_1903_update_18362329_causes_high_cpu/ https://www.reddit.com/r/Windows10/comments/cxmot9/windows_1... It's still clear that Microsoft's QA procedures focus too highly on testing the default configurations rather than the sane configurations.