New Windows 10 VERSION (Yikes!)

 

A new Windows 10 VERSION showed up last night on my computer ready for me to install. So I did. From the brief description I didn't appreciate that it was a new version I was installing, so I started it at 1 a.m. It finally finished at 2:15 a.m., 75 minutes later. And I have an SSD, which means that baby did some serious installing.
Here are the details:

Announcement: Feature Update to Windows 10 Version 2004

From the ABOUT section:
Edition: Windows 10 Home
Version: 2004
OS build: 19041.329
Experience: Windows Feature Experience Pack: 120.2202.130.0

From the Update history section:
Feature update to Windows 10, version 2004

And then, just because it wasn't quite late enough, there was an update to .NET Framework 3.5 and 4.8 for Windows 10 Version 2004 x64 (KB4552925)

and an update to Flash Player:
Security Update to Flash Player...(KB4561600)
In the description of this update was this statement:
Adobe Flash Player will go out of support by December 31, 2020. For more information, see Adobe Flash end of support on December 31, 2020.

Phil

--
"No misfortune is so bad that whining about it won't make it worse."
<<Page 2

mucking about in the registry

John from PA wrote:

See the article at https://www.bleepingcomputer.com/news/microsoft/this-registr.... Note that some of the article involves a registry hack..Use some caution if you never modified the registry.

I have modified the registry when necessary, but why muck about in the registry when Windows Update will simply overwrite my changes in the future?

Also, Microsoft's point about delaying feature upgrades for too long is well taken. How can they write security updates for PCs that range from fully upgraded to never upgraded?

dobs108 smile

No new driver did install today

Lost Anyway wrote:

that message appears when one or more pieces of hardware in your PC has a driver that is not yet compatible with the Windows update.

Time went by, and for the last couple of days Windows Update has advised me that the 2004 update was available for one my my PCs and to click when I wanted to download and install. I've not done any driver update since the previous "wait a while" message.

This was my newest and fastest PC, with a pure SSD C: drive, and not very much clutter on it. The more ordinary incremental updates take about 5 minutes.

The 2004 feature update took about 45 minutes. The good news is that a couple of side effects I did not enjoy on my laptop install did not happen. So maybe they really have fixed some things.

My biggest machine also shows it as ready to install. I'll wait a couple of days to some time when I've got at least a couple of hours free to sit and read a book while it proceeds. That machine has a hybrid C: drive, and installs take much longer on it. It also has a lot more clutter.

--
personal GPS user since 1992

2004 is fine

I'm the OP on this thread, and I'm not having any problems with the 2004 level. As a matter of fact I installed the latest update to that update just yesterday. Again no problems.

Phil

--
"No misfortune is so bad that whining about it won't make it worse."

Windows 10 fixer upper !!!!

One of my laptops just had a fatal crash, so I bought a new one which came with Windows 10 preloaded.

I absolutely hate the "TABLET" look as well as the "Start" menu of Windows 10 which was basically hoisted upon us with Windows 8. I also do NOT like the way it installs any of my programs and they are hard to find !!

This website will tell you how to go from the Tablet look back to the "DESKTOP" look.

https://www.businessinsider.com/how-to-turn-off-tablet-mode-...

And for the "Start" menu, this is the little program I like.
It is called "Classic Shell" and you can download it here.

http://www.classicshell.net/downloads/

This 3 minute Youtube clip shows you what it looks like and how to set it up.
https://www.youtube.com/watch?v=W9FsGqdwi3g

--
Nuvi 2797LMT, DriveSmart 50 LMT-HD, Using Windows 10. DashCam A108C with GPS.

HD machine almost four hours

My primary daily use machine had been offering the 2004 upgrade for just a few days. When I clicked on the "do it" button yesterday, although I did not click on the check for more button, it looked anyway, and discovered that it wanted to install a .NET update as well. The two together took three hours and fifty minutes.

This it not a slow machine, with an i5-4690K CPU. The C: drive is a Seagate hybrid drive. While the hybrid feature considerably speeds up launch of repeated use applications, and routine reboots, it is little help where there is extensive disk activity not repeated from recent previous experience. So the install time was probably similar to that expected for the same machine with a pure hard drive.

I think that was the slowest install I've ever done.

--
personal GPS user since 1992

It might not have been your machine...

archae86 wrote:

My primary daily use machine had been offering the 2004 upgrade for just a few days. When I clicked on the "do it" button yesterday, although I did not click on the check for more button, it looked anyway, and discovered that it wanted to install a .NET update as well. The two together took three hours and fifty minutes.

This it not a slow machine, with an i5-4690K CPU. The C: drive is a Seagate hybrid drive. While the hybrid feature considerably speeds up launch of repeated use applications, and routine reboots, it is little help where there is extensive disk activity not repeated from recent previous experience. So the install time was probably similar to that expected for the same machine with a pure hard drive.

I think that was the slowest install I've ever done.

Keep in mind that download speed depends on the slowest part of the entire process. That can mean that Microsoft’s servers could have bandwidth issues do to heavy traffic (some updates came out last night). Microsoft’s servers could be fine as well and you internet provider is suffering bandwidth issue due to people working at home, browsing, etc.

As far as disk activity, tons of stuff is removed, not just over written and it is the removal followed by the write operation that can cause the high disk activity.

--
John from PA

Thanks, plunder

Thanks, plunder, for checking whether you could defer updates in Win 10 2004, and I'm glad to hear that the big upgrade to 2004 has caused you no issues. I have had problems with sound and printers from some of the earlier "Feature Updates" (though not when I upgraded from 1809 to 1909). Most people do fine.

Remember there is a big difference between "Feature Updates" which Microsoft makes available once or twice a year vs. the monthly "Quality Updates." Normally it is the Quality Updates that have security patches and bug fixes, not the Feature Updates. I do the Quality Updates every month, though not immediately upon release, but always within 30 days. It's the Feature Updates that I want to put off for 6-12 months, and I've been able to do that with the 1809 and 1909 versions. But according to the Computer World article dobs108 linked to above ( https://www.computerworld.com/article/3564597/microsoft-stri... ), Win 10 version 2004 indeed no longer allows this, even for Pro users; you may be able to defer some updates for a month, but not for a year, in the location you specify. There are workarounds for Win 10 Pro users, but they are less convenient and may yet be undermined by Microsoft.

--
"141 could draw faster than he, but Irving was looking for 143..."

Supposedly you can still defer

Lost Anyway wrote:

Win 10 version 2004 indeed no longer allows this, even for Pro users; you may be able to defer some updates for a month, but not for a year, in the location you specify. There are workarounds for Win 10 Pro users, but they are less convenient and may yet be undermined by Microsoft.

Supposedly you can still defer for a year by doing the following although I can’t verify it since I don’t have 2004 (yet).

To enable this feature, open Start, type group, and select “Edit group policy” to open the Local Group Policy MMC (Microsoft Management Console). Then, navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business. Then, in turn, select “Select when Preview builds and Feature Updates are received” and “Select when Quality Updates are received” and set each to Enabled.

This won’t return the “Choose when updates are installed” option in the Advanced Options page of Windows Update. Instead, you will have to configure the deferral timeframe inside of the Local Group Policy MMC with either option opened. Quality updates can be deferred up to 30 days and feature updates can be deferred up to 365 days as before.

Note also that making this change will add a prominent “*Some settings are managed by your corporation” message to Windows Update as well.

--
John from PA

It took a long time

John from PA wrote:
archae86 wrote:

My primary daily use machine had been offering the 2004 upgrade for just a few days. When I clicked on the "do it" button yesterday, although I did not click on the check for more button, it looked anyway, and discovered that it wanted to install a .NET update as well. The two together took three hours and fifty minutes.

This it not a slow machine, with an i5-4690K CPU. The C: drive is a Seagate hybrid drive. While the hybrid feature considerably speeds up launch of repeated use applications, and routine reboots, it is little help where there is extensive disk activity not repeated from recent previous experience. So the install time was probably similar to that expected for the same machine with a pure hard drive.

I think that was the slowest install I've ever done.

Keep in mind that download speed depends on the slowest part of the entire process. That can mean that Microsoft’s servers could have bandwidth issues do to heavy traffic (some updates came out last night). Microsoft’s servers could be fine as well and you internet provider is suffering bandwidth issue due to people working at home, browsing, etc.

As far as disk activity, tons of stuff is removed, not just over written and it is the removal followed by the write operation that can cause the high disk activity.

I did the update to 2004 starting around 1 a.m. EDT and I have an SSD and my CPU is an Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz and it took around three hours from start to finish. I was ready to pull my hair out by the time it finished.

Phil

--
"No misfortune is so bad that whining about it won't make it worse."

Windows 10 Ver. 2004 Stuck At 100% Download

After having the Windows 10 ver. 2004 on my Windows update queue for weeks, yesterday I finally went ahead with the download and update.

For the first time I experienced a problem with my Window update. The download showed 100% completion with no further action, for at least a 45 minute wait. Stopped, dead, no action! At times I've had more than a minute or two to pass from for the download to transition to the installation of the downloaded file but this time it was stuck at 100% download.

A Google search found several methods to fix the problem but several I tried didn't work. Finally I found a Youtube video that addressed the problem that allowed me to find a fix. The video showed two methods. The first suggested method didn't work but the second one did. shock After performing the second procedure, I downloaded the update again and the update process was uneventful on the 2nd go round.

https://www.youtube.com/watch?v=ueNfncM5X34

thanks

Thanks for the troubleshooting video.

Same here my pc has been

Same here my pc has been blocked since May even though I try to update via windows update

--
NickJr Nuvi 3597LMT

.

mcginkleschmidt wrote:

A Google search found several methods to fix the problem but several I tried didn't work. Finally I found a Youtube video that addressed the problem that allowed me to find a fix. The video showed two methods. The first suggested method didn't work but the second one did. shock After performing the second procedure, I downloaded the update again and the update process was uneventful on the 2nd go round.

https://www.youtube.com/watch?v=ueNfncM5X34

I've been doing that since 15+ years ago while troubleshooting WinXP automatic updates.

If you can't remember the commands (net stop wuauserv, net stop bits), look in Services app. Click Start button and type "services" without the command, right mouse click and run Services app as Administrator. The corresponding service names are:

Windows Update
Background Intelligent Transfer Service

It may be easier to just click Stop and Start buttons. Some users may find it easier to use net stop/start commands on the elevated Command Prompt.

The idea is to clear the folder that Windows uses to store downloaded updates and start over. Before clearing the folder, WUAUSERV (or Windows Update) service must not be running.

Thanks for the update

Been wondering if there were bugs or if it was running smoothly.

Updated to 2004 a few days ago

Everything went smoothly and reasonably quickly and my rig is running just fine.

Procedure

chewbacca wrote:
mcginkleschmidt wrote:

The idea is to clear the folder that Windows uses to store downloaded updates and start over. Before clearing the folder, WUAUSERV (or Windows Update) service must not be running.

The procedure is outlined at https://www.alttechnical.com/knowledge-base/windows/89-clean...

If you find yourself running out of hard drive space, it is a good idea to check the C:Windows_SoftwareDistribution folder size. Depending on what updates you've done, the folder size can be in the GB range.

--
John from PA

Keep in mind, MS gives you a

Keep in mind, MS gives you a limited window to revert. It is not a few weeks.

10 days to revert a windows update or upgrade

For years, up to 2016, Microsoft gave a user up to 30 days to be able to revert Windows update or upgrade. Since then a user only has 10 days. After that, if the update or upgrade isn't working, you have to start from scratch, wipe your OS drive, and reinstall the old version, assuming you still have it, along with all your apps.

--
"141 could draw faster than he, but Irving was looking for 143..."
<<Page 2