Windows 10 Announced - Released 29-Jul-2015

Windows 10 2004 upgrade gets blocked due to unsupported settings

https://www.bleepingcomputer.com/ne...ade-gets-blocked-due-to-unsupported-settings/

 

Microsoft's new Windows 10 Alt+Tab plan looks like a mess
July 6, 2020
https://www.bleepingcomputer.com/ne...ew-windows-10-alt-tab-plan-looks-like-a-mess/

 

How to enable Windows 10's hidden features using Mach2

https://www.bleepingcomputer.com/ne...able-windows-10s-hidden-features-using-mach2/

 

Microsoft removes Windows 10 2004 Thunderbolt dock update block

https://www.bleepingcomputer.com/ne...indows-10-2004-thunderbolt-dock-update-block/

 

The list of active Windows 10 2004 compatibility holds

https://www.bleepingcomputer.com/ne...ist-of-compatibility-issues-blocking-updates/

 

How to use Windows 10 File History to make secure backups

https://www.bleepingcomputer.com/ne...ndows-10-file-history-to-make-secure-backups/

 

Just an FYI for 2004 updaters... after upgrading on my system, AMD hi-def audio and many motherboard related drivers reverted to old versions. You might want to check yours.

 

It wouldn't be a bad idea to check all of your drivers each time there is an update such as this. I find it not uncommon for them to replace my USB3 drivers with generic Microsoft drivers that reduce the speed to USB2. They also sometimes blow out the driver for my Creative Labs sound card. They also reset system settings.

At least they don't seem to be turning on "Fast startup" in Power Management anymore. It used to be a real pain to go around all of the PCs in the office and turn it back off. They are still blowing out my custom value for ServicesPipeTimeout in the registry. It is ridiculous that they stop loading services 30 seconds after boot. If you have SQL Server installed it is not uncommon for the service to take longer than that to start. If you have a program that relies on SQL Server and you wonder why it isn't running, there you go.

 

Some Windows Insiders are seeing build expiration warnings
July 21, 2020
https://www.neowin.net/news/some-windows-insiders-are-seeing-build-expiration-warnings

 

Announcing Windows 10 Insider Preview Build 20175
July 22, 2020
https://blogs.windows.com/windowsex...ncing-windows-10-insider-preview-build-20175/

Updated (July 23, 2020):

 

Some AMD PCs are still blocked from receiving today's Windows 10 Insider build 20175
July 23, 2020
https://www.neowin.net/news/some-am...ceiving-todays-windows-10-insider-build-20175

Updated (July 23, 2020):

 

Anyone notice ghosting for deleted/moved files or shortcuts on their desktop after upgrading to v2004 more than usual? It has been very rare to happen to me in the past, but it's happening more frequently since I upgraded.

 

yup, this is the buggiest build in the Windows 10 history. Even the latest Cumulative updates didn't fix it.

 

I never had the issue because when the time came I downloaded the ISO from Microsoft and installed it that way and still don't see any issues. The 2 yearly major Updates I don't like doing it through Windows Update so I always use the ISO to install.

 

Yeah I saw that even when it was still in testing and it is still not fixed.

I went back to 1909 at work and at home. I am skipping the 2004 build for sure. Way too many issues for me.

 

I turned on WU on the 17th and got: https://support.microsoft.com/en-us/help/4560960/windows-10-update-kb4560960 I am staying with 1909, for the time being. It is fine.

 

Microsoft to start pushing out Windows 10 2004 to reluctant upgraders
July 23, 2020
https://mspoweruser.com/microsoft-pushing-out-windows-10-2004-to-reluctant-upgraders/

 

It probably depends on the PC. I have had no issues with it. I think it was 1809 that I couldn't even run on my laptop because it would BSOD at the end of the install as it didn't like my graphics card. It also failed on multiple desktop PCs in the office as it didn't like the Wi-Fi card. At least that was fixable by removing them. Aside from that I have had no major issues with any of them. I've probably had minor issues with all of them but that's always going to be the case. Probably the best thing to do is make an image, test the new build, and roll back if your PC doesn't like it. On the other hand if you're happy with what you have then like the old saying goes, "if it ain't broke, don't fix it".

 

Announcing Windows 10 Insider Preview Build 19042.421 (20H2)
July 24, 2020
https://blogs.windows.com/windowsex...dows-10-insider-preview-build-19042-421-20h2/

 

couldn't have put it better.

 

@Spartan, @Trooper
Thanks for the response. Ugh, I think I'll stick with v2004 for the time being. I don't recall having many problems with v1909, but I don't feel like fooling with installing clean atm, lol, at least not yet. Have either of you noticed, or anyone else ftm, artifacts in your browsers with hardware-accelerated GPU scheduling enabled in the graphics settings in v2004?

 

Well the 20H2 build is a big flop. I wish I had not put both of my personal machines on it. This morning I installed the latest update on my laptop and after logging in I get a black screen. Restarted 3 times, happens every time. Had to roll back a week to a disk image of 2004. Trying to decide if I want to roll back my desktop. It is working but I'd rather have them both on the same version. I guess this is what I get for saying Windows 10 wasn't as bad as some think in a previous post.