Windows 10 update to 22H2?

Topic

New Reply

Yesterday, a little while after starting my computer, I noticed the restart button on the taskbar which generally means there has been an update. Upon checking with Windows Update in settings, it said I needed to restart after an update. However, unlike most updates with a KB number, this just said it was an update to Windows 10. After restarting, the system went through several reboots, similar to what happens during a new feature update. After rebooting, I see Update history now has a second “Feature update to Windows 10, version 22H2” in addition to the one from Dec. 2022 when it originally updated to 22H2. When I click on “See what’s new in this update” it brings up the same items in Windows Tips as the last feature update. I can’t see anything new here. Also, the version number 19045.3930 is the same as before this update. I haven’t been able to find anything online about this supposedly new feature update. Does anyone know why this happened and what has been changed, if anything?

Reply | Quote

Replies

Does anyone know why this happened

It obviously appears windows is downloading and installing updates automatically.  If you’re running Win 10 Pro, you can control this from the Group Policy Editor.

I addition this thread has a lot of current info that will help:

https://www.askwoody.com/forums/search/incontrol/

Consider getting on board with image backups and eliminate the uncertainty and concern from surprise events.  Search “making system image backups” on AskWoody.

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

RobertG wrote:

However, unlike most updates with a KB number,

Drivers, firmware/BIOS… don’t have KB numbers. These should be blocked.

https://www.askwoody.com/forums/topic/comments-on-akb-2000016-guide-for-windows-update-settings-for-windows-10/

Reply | Quote

This was more than just a driver/firmware update. This seemed to be a repeat of the upgrade to Win 10 22H2 that had already been installed in Dec. 2022. My question was why this would just happen spontaneously. All other Jan updates installed without a problem (except for KB5034441 which I have blocked).

Reply | Quote