Microsoft releases KB4462933 for Windows 10 version 1803
While Microsoft is still busy getting Windows 10 version 1809 ready for re-release after what can only be described as anything but a clean launch, it released an update for the current main version of Windows 10, Windows 10 version 1803.
The cumulative update KB4462933 replaces all previous updates installed for that particular version of Windows 10. System administrators should see the update already on Windows Update, WSUS and other Microsoft Update related services.
Note: While it may be tempting to install the update right away, we suggest you wait at least some days before you do so unless you have a proper backup in place or tested the update extensively before deployment on production machines.
Note 2: If you install updates manually, you need to install the latest servicing stack update first on the machine before you install KB4462933 as the update will fail otherwise. The update can be downloaded from Microsoft's Update Catalog website.
KB4462933 is a big update that includes dozens of fixes but no security updates. The update brings the build of the operating system to version 17134.376 when it is installed on a device.
Here is what is changed and fixed by KB4462933:
- Admin: sysprep /generalize failed in audit mode.
- Admin: Event Log service stopped responding until restart. Occurred when the event log was full and "Do not overwrite events" was selected.
- Admin: when calling CreateProcessWithLogonW(), Access Denied error code "0x5" was thrown on systems with more than 4 Gigabytes of memory.
- Admin: AccountName in the Event Log for Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event ID 7Â appeared corrupt sometimes.
- Admin: TLS 1.0 or TLS 1.1 could not be disabled when FIPS mode (Federal Information Processing Standard) was enabled.
- Admin: handle leaks issue when using client authentication certificates with TLS.
- Admin: TCP connections for apps running on Windows Container failed sporadically.
- Admin: App-V packages failed because of missing file or DLL errors.
- Admin: restore of container snapshots failed because of missing files.
- Admin: fixed an issue that prevented Immediate Tasks from being deleted.
- Admin: issue prevented Scheduled Tasks from being executed until a user logged in.
- Admin: Fixed reporting issue that implied incorrectly that user rights Group Policy settings were not applied.
- Admin: Fixed Scheduled Task issue where tasks would not execute at the expected time.
- Admin: System.Security.Cryptography.Algorithms reference load issue after July 10 and August 14 cumulative updates.
- Hardware: legacy Bluetooth Basic Rate device inbound pairing issue.
- Hardware: operating system stopped working when a Bluetooth device is removed.
- Hardware: Call Control issue that caused the audio service to stop working with error messages such as Exception error 0x8000000e in btagservice.dll, Exception error 0xc0000005 or 0xc0000409 in bthavctpsvc.dll, or Stop 0xD1 BSOD error in btha2dp.sys.
- Hardware: Precision touchpad issue that caused applications with child windows to stop processing mouse inputs.
- Hardware: multi-monitor issue that rendered an app in full-screen mode incorrectly after changing the display mode.
- Hardware: some applications stopped working after unplugging a tablet.
- Microsoft Edge: some documents did not appear in the debugger of the Developer Tools.
- Microsoft Edge: some extension scripts did not appear in the Developer Tools.
- Microsoft Edge: fixed a Microsoft Edge warning message issue when printing PDF documents.
- Microsoft Office: support Microsoft Office events in the "Limit Enhanced" Group Policy setting list.
- NET Framework: fixed Net Framework applications issue that caused apps to stop working with error "The process cannot access the file <name of temp file>".
- NET Framework: Net Framework support updated for Japanese date formats.
- Other: redenomination of local currency that the Central Bank of Venezuela implemented. Also, updated Venezuela currency information.
- Other: issues with updated timezone information.
- Other: fixed SharePoint Online "couldn't open PDF" issue when printing documents.
- Other: Windows Defender Application Guard would not launch after servicing on Windows 10N devices.
- Other: Fixed clock and date fly-out in Spanish versions of Windows 10.
- Other: application title truncation issue
- Other: Windows 8.1 app stopped working when calling ProjectionManager.StartProjectingAsync API with error code 0x80070057
- Other: some application input text elements stopped responding.
- Other: fixed East Asian text input issue when creating passwords.
- Other: addressed leak issue during window destruction events.
- Other: addressed on-screen keyboard text input issue that made suggested words appear and then disappear.
- Other: fixed issue that prevent apps from displaying popup windows or dialog boxes when in full-screen mode.
- Other: Japanese Calendar view issue that caused navigation across eras to stop working.
- Other: addressed date format issue in the Japanese era calendar. Also fixed GetCalendarInfo when used on a Japanese era calendar.
Now You: Have you installed the update?
Thanks a lot for this very clear sum-up !
Thy shall not find the “Servicing stack update” because they are listed as “Critical update” and no mentioning of servicing stack. Again the best of fail countinues.
After this update, the bug with file associations is still not fixed :(
“No problems reported so far, but itâ€™s only been a few minutesâ€¦”
Probably should wait for at least a few more minutes!
Thanks, Anders. I found my servicing stack update on the Microsoft’s Update Catalog by searching for “Critical Update for Windows 10 Version 1803 for x64-based Systems”.
There is a good reason why there are no known issues thus far. MS is waiting for the beta testers (aka Home users) to get back to them with bug reports.
I’ll be taking Martin’s advice by holding off on this one for a while.
Microsoft must change its way to release and apply updates because users are reaching a level of anxiety and headaches never seen before in the history of operative OS. Twice a year is too much, just considering that Ubuntu are currently releasing long term support versions each two years (with extended support of five years each, again another way to stuck people three years in an old version). Anyway, MS should stuck itself at one version of Windows 10 and just offer new stuff like an optional choice, including any kind of cumulative update and minor updates. New ISOs each six month are just madness and an exploitation of the own MS development team and user’s patience.
Must say I was sweating it a bit but happy to say installed without issue. One thing found was after reboot all icons on the task bar that point to a portable program on a vercrypt partition were missing, easy enough to fix with them already in the start menu.
Just posted a problem with this update on Tenforums to a reply to another poster with the same problem:
One of my old test PCs was on 17134.345, installed KB4462933 taking it to 17134.376.
Got the exact problem as you described – WiFi would work for a while, (anything from 5 to 20 minutes) then I’d have no network access, (browsers or Ping) despite hovering over the system tray WiFi icon and it saying “Internet access”
Then after a few seconds, yellow warning, and no connection.
I’m using a cheap, but good external WiFi dongle on this PC and the problem could be temporarily fixed by ejecting the dongle and reinserting it – then it happened again. Cycle may be repeated at will.
Looked for updated drivers for the dongle – none found.
Uninstalled KB4462933 so now back to 17134.345 and all is OK
Tried to install this update last friday, after restart at 30% completion, nothing to see anymore except for “the eternally spinning wheel of doom”. Had to revert to 17134.345 in safe mode (return to prior ‘anchor point’ in regular mode did not function at all).
Now everything is back to normal and I temporarily blocked updates in my settings (MS had been doing quite OK for quite some time so I guess they found it to be no more than fair to screw it up for the ‘guineapig-user’ once again!
I am having some wifi issues with the new update. My version is 1803 with OS build 17134.345 and then it updated today to 17134.376 and I still have wifi issues. Should I uninstall the Intel(R) Dual Band Wireless-AC 7265? I’ve heard that helps.
Anytime the wifi disconnects, I run the trouble shooter and it says “There might be a problem with the driver for the wi-fi adapter” and then the troubleshooter fixes the issue and I can connect back to the wifi, but then it disconnects again.
Is this a common problem? How can I fix it?
The wifi is driver version: 18.104.22.168
I ran a troubleshoot for my computer and it said the System Fireware has a driver problem, but troubleshooting could not identify the problem.
The KB44622833 update was just applied automatically to 1803 on one of my machines and I can report the following difficulties:
1. All personalization was lost
2. Some previously installed apps are no longer installed (Office 365, WLM so far)
3. All files in the Pictures and Videos folders are gone
Can anyone state, as PDC performed, an instruction set for blocking updates, clear with appropriate key strokes as the verbs (instead of saying “go to xxxxxx, say what the actual keystrokes are to do so).
Since my Win10 is in Dutch, I’ll do my best to stick as close as possible to what I guess to be the correct English terminology.
– Click on the Windows logo in the taskbar (utmost left at bottom of your screen – if that’s where your taskbar is);
– then click ‘Settings’ (the daisy wheel) and the settings window will open;
– there you click ‘Updates and Security’;
– in the upcoming ‘Windows Update’ window click ‘Advanced options’;
– in that window you will see “Interrupt updates” as the second paragraph: probably the elliptical shape will have a black dot in it on the left side and the text “Off” to the right of it;
– click on the ellipse and it will turn blue with a white bullet on the right side and “On” to the right side;
– below it you will see a text appearing (if you would do it today say): “Updates have been interrupted till 4/12/2018”;
– return to the next higher level in the ‘Settings window’: there it should read now “Updates interrupted – Restart updates is planned for 4/12/2018.
Till that date, no more automatic updating for major updates should occur.
Hope this was useful.
Take a look at this thread
Read the part where Warmikez and I are discussing the driver issue. Warmikez has solved it – I plan to get to it when I have the time.
I have a wifi problem after this update. The wireless adapter disappears and I cannot connect to wifi except using ethernet.
See my update to my October 30 post here….https://www.tenforums.com/windows-10-news/120400-cumulative-update-kb4462933-windows-10-v1803-build-17134-376-oct-24-a-5.html#post1510301