Yes indeed. I know I can laugh 😆 a few months ago I downloaded the .iso file 1 to 2 times when the Reset this PC function didn't work and I had to Reinstall via the Installation Media.
Cumulative updates - November 2020
This is a summary of the cumulative updates released on November 10th for all the supported consumer releases of Windows 10.
- Windows 10 version 2004 and version 20H2 - KB4586781, Build 19041 and 19042.630
- Windows 10 versions 1903 and 1909 - KB4586786, Build 18362.1198 and 18363.1198
- Windows 10 1809 - KB4586793, Build 17763.1577
IMPORTANT
Release notes are changing! To learn about the new URL, metadata updates, and more, see What’s next for Windows release notes.
IMPORTANT
Windows 10, version 1809, will reach end of service on November 10, 2020 for devices running Windows 10 Home, Pro, Pro for Workstation, and IoT Core editions. These devices will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.
IMPORTANT
Windows 10, version 1903 will reach end of servicing on December 8, 2020. To continue receiving security and quality updates, Microsoft recommends that you update to the latest version of Windows 10. If you want to update to Windows 10, version 1909, you must use the Enablement Package KB4517245 (EKB). Using the EKB makes updating faster and easier and requires a single restart. For more information, see Windows 10, version 1909 delivery options.
Windows 10 update history
https://support.microsoft.com/en-in/help/4529964/windows-10-update-history
Windows 10 release dashboard
https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004
Windows 10 message center
https://docs.microsoft.com/en-us/windows/release-information/windows-message-center#407
Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
*Important:*Users posting replies referring to their own websites would be considered as Spam and would be suspended from this community.
(If you have recommended this discussion and are looking for the unsubscribe button, please hit subscribe below, and a dialogue will open with the unsubscribe choice.)
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
255 answers
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2020-11-15T04:19:35+00:00 -
Anonymous
2020-11-15T03:35:30+00:00 You can laugh! I know you are busy but Thanks for answering about the file size. I thought at first it was too small, but if you
say it's correct I believe in you - Computer Guru! Take Care.
-
Anonymous
2020-11-15T02:46:46+00:00 not. I'm not laughing for now.
true .iso file about 4 GB Depending on your Windows 10 architecture being installed. Please wait for someone to answer your Question about .iso files being opened with 7 Zip archiver.
I'm busy for now.
-
Anonymous
2020-11-15T01:05:07+00:00 I keep having BSOD issues with windows 20H2 even with the November updates, PC is fully updated. (OS Build: 19042.630)
Constantly with dxgmms2.sys, Dump info below, Before anyone says its to due with a faulty driver...
I've already used Display Driver Uninstaller numerous amount of times and also I never had this issue with any of the previous versions of windows from 2004 through to 1803...
I've also tried countless full windows reinstalls with completely cleaning/formatting the drives to ensure nothing remains and still the issue remains...
Ever since I got 20H2 I constantly have this issue occurring upon shutdown.
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000033, The subtype of the bugcheck:
Arg2: ffffc304d8b8eb30
Arg3: 0000000000000000
Arg4: 0000000000000000
SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+27799
MODULE_NAME: dxgmms2