Susan recommending version 2004

Topic

New Reply

Per today’s Newsletter, Susan Bradley recommends Version 2004

All clear for 2004

If you are currently on Version 1909, or even 1903, I’ll urge you to plan on updating to at least 2004. To ensure that you only get offered 2004 and nothing but 2004, Windows 10 Home won’t cut it. You’ll need to be on Windows 10 Professional.

Now you’ll want to use the Targetreleaseversion setting in order to set the specific feature release version to 2004.

To enable this setting, click in the Windows 10 search box, type in group policy, and look for the option “Edit group policy.” In the upper-left corner, look for Local Computer Policy. Click on Administrative Templates, then on Windows Components. Scroll all the way down to the bottom and find the Windows Update folder. Click to expand Windows Update. Click on the folder Windows Update for Business. Click on “Select the target Feature Update version.” In the group policy box, enter the feature version name — for example, if you want to ensure your machine stays on 2004, enter 2004.

In addition to the above, could someone (PKCano and members) advise those of us on 1909 what the Feature Update Deferral days number would be to put in Windows Updater Advanced options setting to trigger download of version 2004.

Also pls include a listing of the major changes that 1909 users will face when moving to version 2004, such as Windows Updater Advanced Option setting going away and what to do, and wasn’t Device Manager going to change regarding losing driver updating?  Changes to make after installing 2004 and before re-connecting to the internet.

Commentary on these as well as any others would be very helpful.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Replies

Does anything else change within the Windows Updater GUI with version 2004? Maybe some screen shots?
(Sorry, missed my edit time window)

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I am also running Windows 10 Professional v1909 and it has been my understanding that I can’t now obtain v2004. I have a flash drive with 20H2 on it for the future, but my computer came with 1909 instead of 2004 and it was too late by the time I picked up on it, so I am following this thread.

I guess the other question would be is 20H2 safe? Based on Susan’s article today it sounded like she was advising 1909 people to upgrade to preferably 2004 or alternatively 20H2. Or did I miss something?

Reply | Quote

You can download 2004 ISO from Heidoc.net.
You can run the ISO from your desktop (double click, open and run setup.exe)

Before upgrading make a full image backup of your system to external HDD..
Disconnect from Internet.
Run the upgrade.
After the upgrade go over ALL settings including deferrals…
Set Targetreleaseversion to 2004.
Reconnect to the Internet.
Apply monthly security updates if needed.

6 users thanked author for this post.

ceruleandaze, joltar, Coldheart9020, jburk07, John18, Microfix

Reply | Quote

Stay tuned for replies to my question:

Tex265 wrote:

In addition to the above, could someone (PKCano and members) advise those of us on 1909 what the Feature Update Deferral days number would be to put in Windows Updater Advanced options setting to trigger download of version 2004.

I am certain that by playing with the Feature Update deferral days entry in the 1909 Windows Update GUI that we can get versions 2004 or 20H2 (depending on the number of days entered) to be offered via the Updater.

 

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

In Win10 Pro you can use Group Policy to upgrade v1909 to v2004 or v20H2 by setting TargetReleaseVersion. See AKB2000016 Section 3 and 5 for information.

You do not have to use the ISO.

2 users thanked author for this post.

Fred, John18

Reply | Quote

I’m considering 2004 safe.  I would recommend using the targetreleaseversion setting (see the references above) to choose 2004.   The ISO is also another way to get it.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

jburk07, John18

Reply | Quote

I’m making a special one-time external image backup now and will try the procedure when I get back home.  I already burned the ISO, but will try the method within Windows first.

Thanks “Boss” and the rest of you.

Reply | Quote

Thanks everyone.  I did do the full image backup, then the TargetReleaseVersion via the Group Editor and then verified the change had been made via RegEdit.

I also changed my Feature Version Release defer time in Settings>Windows Update>Advanced Settings from 365 days to 185 days and then clicked on Check For Updates and 2004 is indeed downloading without doing the ISO.

I am almost done with the download so I will be closing things while 2004 installs.

Thanks again.

2 users thanked author for this post.

ceruleandaze, jburk07

Reply | Quote

John18 wrote:

also changed my Feature Version Release defer time in Settings>Windows Update>Advanced Settings from 365 days to 185 days

You should set the Feature Deferral to 0 (zero) or “Not configured.” If you have TRV set, deferral days will be ignored. TRV will keep you from getting upgraded until you change the version number.

You don’t need Feature Deferral days set.

5 users thanked author for this post.

ceruleandaze, Coldheart9020, Chris B, jburk07, John18

Reply | Quote

Thanks.  I have fixed that.

Reply | Quote

I have TVR set for 1909 and Feature Version Release defer time in Settings>Windows Update>Advanced Settings set for 365 days.  The update to 2004 is still being pushed to my computer.  I’ve double checked the TVR setting and it is set up as recommended.  It does not appear that the TVR setting is overriding the deferral setting.

Any thoughts on this would be welcome.  I do plan to upgrade to 2004 once I have developed all of the recommended backups.

Reply | Quote

As posted in the past, Microsoft will disregard stop/deferral settings and forcibly push new feature update when they think it time.

Reply | Quote

I could understand it if I was being pushed from 1809 to 2004, but not 1909 to 2004.  If this is the case, then all the TVR discussion is fundamentally a waste of time, and time is better spent following the wushowhide approach.

Reply | Quote

Are you already on 1909?

cheers, Paul

Reply | Quote

See AKB2000016 Section 5 for information on Windows Update settings for v2004 and later.

Reply | Quote

In my (not so) humble opinion, don’t use the days method. Use the targeted release setting. It’s MUCH safer.

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

ceruleandaze, Chris B, John18

Reply | Quote

So if we set the targeted release entry within Group Policy to 2004, to what days delay number  do we set the Feature Update in the Windows Update GUI Advanced options entry to? (mine currently 365 days).

Pls discuss any other changes/settings we need to be aware of with 1909 to 2004.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

If you use TargetReleaseVersion, set deferrals to 0 0r 1, as they are going to be ignored anyway.

2000016: Guide for Windows Update Settings for Windows 10

Reply | Quote

[Bob99]

I’m on 10 Pro 2004 fully updated to include the December patches, and I just did the following:

With Feature Update deferral days set to 365, I set Target Release Version to 20H2, and it showed up in wushowhide. Once I changed TRV back to 2004, 20H2 didn’t show in wushowhide.

Since 20H2 has only been out at this writing for about 90 days give or take, the Feature Update deferral setting of 365 days was ignored and the TRV setting was followed instead.

So, for those wondering about 20H2, you have to set that exact value (20H2) in order to see it. At this time, however, 20H2 is not advised to be installed.

For those wanting to go to 2004 from 1909 or 1903, follow instructions in AKB2000016 in setting TRV to “2004”. For those using a Home edition of Windows 10 instead of a Pro edition, the change will have to be made in the registry, I believe. Please see the aforementioned AKB for full details. Direct links to it can be found here and here in this thread.

 

• This reply was modified 4 years, 1 month ago by Bob99. Reason: eliminated duplicative link to AKB

1 user thanked author for this post.

ceruleandaze

Reply | Quote

Questions on options updating from 1909 to 2004 pro:

— To Update within Windows update group policy set to “2004”:

Q1: Should I disconnect from internet once the 2004 file downloads but before installation?

Q2: Will this process also install the January updates as well that are still Defcon 2?

— To update using iso from Heidoc:

As the Heidoc iso is dated May 2000, when is safe to update as the Jan 2021 updates are still Defcon 2?

I do have an iso that I made via Media Creation Tool in October right before the Cert problem was discovered so I suppose it cannot be used.

This is a new experience for me as I have not installed a Win 10 update before. One pc has 1909, the other 2004 (both pro).

Thanks for any advice.

Reply | Quote

If you use an ISO, the installation is up-to-date ONLY on the day the ISO was made. So if you use an ISO made in Oct 2020, what you get is not up to date.
Using the ISO to upgrade, if you DO NOT disconnect from the Internet during the installation, the process will upgrade you to the latest Build of the latest version of Win. That is Dec 2021 and v20H2.
If you disconnect from the Internet, it cannot do this, but you will have to update once complete. That you can control by setting Windows Update in the Settings App.

If, instead, you use TargetReleaseVersion setting at 2004, you will upgrade to v2004. Instructions for this are in AKB2000016, Section 2 for Win10 Home and Section 3 and 5 for Win10 Pro. There are screenshots at the bottom to help you find the settings. It is a much easier way to upgrade.

7 users thanked author for this post.

Jorge Troitiño, jburk07, MikeyD215, JCpharm, hms, ceruleandaze, Fred

Reply | Quote

The 1909 pc is set per your original AKB000…16 group policy settings. Before updating, I will change the settings to target release date of “2004” and set feature deferrals to “0”.

1. Using the Windows update method, should I disconnect from internet after the download and before installing? I do not have a MS account and do not want one.

2. Should I wait to update to 2004 until nearer the end of January to see if there are any problems with the January updates?

Thanks for your advice now and many times previously.

Reply | Quote

You do not have to disconnect from the Internet if you use the TRV setting.

It is going to update you to January patches if you do it now. Try to hide KB4535680 (the Secure Boot DBX patch, if it is offered) with wushowhide first, clear the queue, then you are probably safe to go ahead.

Or you can wait and see if there are any other problems with Jan patches.

Either way, you will get v2004.

3 users thanked author for this post.

jburk07, MikeyD215, hms

Reply | Quote

I will wait a week or so to see if any major Jan. update problems and will avoid the Secure Boot patch.

Thanks  so much.

 

Reply | Quote

[EP]

the updated 2004 ISOs made in late October 2020 (that have build 19041.572, not the older 19041.x builds before this) include the Cert bugfix but were released only to MSDN/MVS subscribers (lucky them!) but the updated 2004 ESDs w/ 19041.572 were also released only thru WSUS in early November 2020

edit – so I downloaded this v2004 build 19041.572 ESD install media directly from MS windows update server and then converted it to a working ISO using the decrypt-multi-release tool, then run the 2004 installation from there.

• This reply was modified 4 years, 1 month ago by EP.
• This reply was modified 4 years, 1 month ago by EP.

Reply | Quote

My Win 10 Home pc does not show the “Windows PowerShell (Admin)” choice. I only have “Windows PowerShell”, “Windows PowerShell (x86)”, “Windows PowerShell ISE”, an “Windows PowerShell ISE (x86)”. I do not know where to put the registry entries now.

Reply | Quote

Those are the standard All Apps entries on the Start Menu for everyone under Windows Powershell.

But you can access Windows PowerShell (Admin) by right-clicking the Start button for the Win+X Quick Access menu.

Or right-click Windows Powershell in the All Apps menu, then More, then Run as administrator.

Reply | Quote

None of your suggestions work for me. How do I set TRV in W10Home now?

 

I can do regedit VERY CAREFULLY if you advise me what/where to do!

Reply | Quote

[geekdom]

Read here and be careful with the registry:
https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/#post-2286499

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

• This reply was modified 4 years, 1 month ago by geekdom.

Reply | Quote

Ken,

Refer to PKCano’s comments from January 18th (above). Use his AKB2000016, Section 2 for Home users. If you are good at Regedit, take the directions to create the two lines as he has described.

“For Win10 Home you can manually create the Registry entries as described in Section 3 at this location:
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. REG_DWORD = TargetReleaseVersion, value = 1

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, REG_SZ = TargetReleaseVersionInfo, value = 2004 (or specified current version)”

If you could not find Power Shell (Admin), you find it by right clicking on Power Shell and “Run as Admin”, then follow the Power Shell directions to enter those two lines, exactly as shown in AKB2000016, Section 2.

Gunny

Reply | Quote

[Ken]

“What happens when you right-click the Start button?” I get a long menu of items, none of them PowerShell.

“What happens when you right-click one of the four Windows Powershell entries in the Start/Apps menu?”

I am abbreviating Windows PowerShell to WPS:

a. : WPS: run as admin, run ISE as admin, WPS ISE, run as admin, open file location. If I run as admin, it opens a command prompt window at Windows\Systems32

b. WPS (x86): run as admin, open file location

c. WPS ISE: run as admin, open file location

d. WPS ISE (x86): run as admin, open file location

 

 

• This reply was modified 4 years, 1 month ago by Ken.

Reply | Quote

Ken wrote:

a. : WPS: run as admin,

Use this.
Copy/Paste each command into the prompt one at a time then hit “Enter”
Be sure you go to the end of the line when you copy.
On the second command, you need to be sure it says 2004 instead of 1909.

1 user thanked author for this post.

Ken

Reply | Quote

OK, now I understand, did it. Now should I resume updates or just wait until just befopre my pause ends (2/6) at which time I’ll do the metered connecting thing.?

Reply | Quote

Turn ON Metered connections.
Resume updates.
Use wushowhide to hide anything you don’t want.
Reboot your computer.
Wait for WU to rescan on its own and be sure only v2004 is offered.
Turn OFF Metered connections and upgrade.
After the upgrade, turn Pause back on.

1 user thanked author for this post.

Ken

Reply | Quote

Additional instructions please: I have EaseUS Todo Backup Home v 13.0: I run a disk 0 backup, full system backup, file backup, Outlook backup every day. I will make a new boot disk. If my system were to crash, which backup do I restore and in what order? I assume that once it boots up, I will have to download some programs such as EaseUS or others, or will these be restored with from disk 0 or System backups?

Reply | Quote

[Paul T]

Depends on what crashed, but if it’s just Windows you only need to restore the system backup.

Create an EaseUs recovery USB now. Test it by booting to it and you will see that it is ready to recover.

cheers, Paul

p.s. create a new topic if you want more detail on backup or restore.

• This reply was modified 4 years, 1 month ago by Paul T.

Reply | Quote

Thank you! I don’t remember…. how do I boot to the usb?

Reply | Quote

Am trying to create the boot usb. Formatted it but TdB keeps asking me to format. Should it be to a different file system? Choices are NTFS, FAT (deault), FAT32, exFAT.

Reply | Quote

[Paul T]

Format it as FAT32.

Once you have created the recovery USB (Select “Create WinPE emergency disk”):
Plug it in
Hold down the Shift key while clicking Restart
Select the option to boot from USB

Wait while the USB loads, it can take 5 minutes.

You should be able to navigate to the backup files in TdB – don’t actually restore.

 

• This reply was modified 4 years, 1 month ago by Paul T.

Reply | Quote

Thank you! Now looking at my Lenovo E570, W10 Pro v1909: I have read the string about the Conexant drivers which are incompatible with version 2004, but cannot figure out if I have those versions. One of the posts has a link which mentions some dll files, but does not indicate where to find those dll files. I have asked various questions there, but never received any responses.

This pc has Conexant SmartAudio HD version 10.0.18362.1 and also version 8.66.76.61. Lenovo has never offered updates through Lenovo Vantage.

MS now offers a Lenovo-Monitor- 6.14.7.0 update: Any optional monitor updates offered by Lenovo are much earlier versions! I have hidden the MS update.

Not sure what I should do.

Reply | Quote

Read this Microsoft’s post regarding Microsoft’s own workaround to fix Conexant ISST audio drivers blocking 2004/20H2 updates.

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-20h2#417msgdesc

1 user thanked author for this post.

Ken

Reply | Quote

<h5>I am OK on the first section, but in Sound, Video and Game Controllers my Conexant version falls within the range mentioned. If I understand this correctly, I don’t have to do anything, the 2004 update will be postponed by MS until this has been resolved. I do not understand the stuff about safeguards and update compliance. Two safeguards are OK, the other two are not…. what does this all mean?</h5>

Reply | Quote

PKCano wrote:

Reboot your computer.

Regarding #2338554, does “reboot” mean “shut down” and “power back up”?
or does it mean “restart”?

Reply | Quote

As far as Windows is concerned there is no difference. What might make a difference is turning off fast start.

cheers, Paul

p.s. that link doesn’t seem relevant

Reply | Quote

Paul T wrote:

p.s. that link doesn’t seem relevant

Sorry, the link should be #2338179.

Reply | Quote

Noticing your comment about turning off Fast Start, I had to turn Fast Start off for both my 1909 and 2004 pcs. They were randomly giving off error reports in reliability history that Windows was not shut down correctly. That was not true. After turning Fast Start off (not recommended by MS), I have not rec’d this error msg. in months. Also, I do not notice any lag in startup – although both have SSDs.

Reply | Quote

There is further discussion of the question of what “reboot” means and a better answer to it at #2338597.

Reply | Quote

I turned metered connections ON, then resumed updates. 4599301 and 4535680 were downloaded, then pending installation. 4023057 pending download, Malicious software removal tool pending download. 2004 “getting things ready”.

I thought nothing would download if metered connections ON.

I waited for 2004 to be “ready”. When that happened, “pending download”. So I hid everything else: even the ones which were shown to have been downloaded were hidden, and proceeded with your instructions. A few hours later, 2004 was successfully installed! I then unhid 4023057 and MSRT and installed both, now all up-to-date!

Thank you for all your help!

 

Reply | Quote

[Paul T]

Resume updates may ignore all your settings.

Leave metered on but do not pause is the easiest way to manage Windows Home.

cheers, Paul

• This reply was modified 4 years, 1 month ago by Paul T.

Reply | Quote

Maybe a bit off-topic but I just did a fresh install of 20H2 yesterday. Haven’t run any benchmarks but it feels a bit snappier than 1909 and 2004 to me. Also, no problems noted…. so far!

Reply | Quote

Well, that was painful.

I did the upgrade to 2004 using the TRV method. About a hour and a half for the download and install. Another 4 to 6 hours removing the junk that Microsoft thinks my version of Windows needs, disabling the un-needed services, going back through Group Policy and Task Scheduler to make Windows, my Windows.

Come on, Microsoft, it’s a computer, not a Xbox, a phone……

1 user thanked author for this post.

baggins

Reply | Quote

Works great! https://community.spiceworks.com/scripts/show/4378-windows-10-decrapifier-18xx-19xx-2xxx

Reply | Quote

[opti1]

I’m new to Win 10, have Pro, currently on 1909, have not connected online yet, preparing to connect and upgrade to 2004 before proceeding with further setup.

Should configuration settings changes of the kind discussed in this thread and in AKB2000016 be made while logged on to an Administrator account or is it OK to make them while logged on to a standard user account with elevated permissions (assuming one gets prompted for them)?

Same question about updating Win10 in general, do this from an Admin account or is an elevated standard user account OK?

Thanks!

• This reply was modified 4 years, 1 month ago by opti1. Reason: Updated language for clarity

Reply | Quote

You need to be logged in to an Admin account on the computer to make Group Policy settings and do the update.
I recommend you use the TargetReleaseVersion settings exactly like it shows in AKB2000016 Section 5. Set the version at 2004 and only use the settings that it shows for the others. Make the settings offline,  then go onlineand wait for Windows Update offer you v2004 on its own. You will get Jan updates if you do it now (before Feb Patch Tues).

My advice is to hide KB4535680 (the Secure Boot DBX patch) with wushowhide before you update. If you use the “2” (notify download/install) setting, you can hide it and wait for Windows Update to rescan so it doesn’t show up in the queue.

3 users thanked author for this post.

ceruleandaze, hms, opti1

Reply | Quote

Before updating to 2004 by TRV, should I hide a raft of third party Intel and Realtek updates? I did hide KB4535680 and one other earlier KB.

I have set by Group Edit to Not Include Drivers with Win Updates. They are just sitting there as I have not hidden them. Should they be hidden before updating?

Will my Group Edit policy settings be carried over to 2004?

I have installed some Intel updates through Dell update so some of the windows version Intel updates may already be installed by that process.

I want to avoid having the 2004 automatically update all these Intel and Realtek updates.

Thanks.

Reply | Quote

My advice is to get your driver updates from Dell (or whatever OEM manufacturer) and hide the ones from MS. If you have problems, you can try the related MS driver, but you always have the option to roll back the driver in Device Manager if the MS one doesn’t work..

2 users thanked author for this post.

opti1, hms

Reply | Quote

Per your suggestion, I have hiden these; presumably hidden updates  will not install with the new 2004.

I had not hiden these MS drivers as I thought the list would not expand as newer updates would replace the older ones. Suppose I was wrong; the list, especially for Realtek audio, keeps growing, but Dell says I need only 1 Realtek optional update that I never bothered to install for an inexpensive speaker.

Will do the 2004 update once Defcon changes from 2.

Thanks again for your help.

Reply | Quote

Will do the 2004 update once Defcon changes from 2.

The MS-DEFCON level is meant to be for the monthly patches with the KB numbers attached to them, not for the updates/upgrades from one version to another such as going from 1909 to 2004.

Susan has given the all clear to update to 2004 from earlier versions of Windows 10, so go ahead and take the plunge when you feel comfortable doing so.

1 user thanked author for this post.

opti1

Reply | Quote

And if the patches are included in the update?

You can wait a bit, it’s only a week away.

cheers, Paul

Reply | Quote

I’m running Win10 Pro 20H2 with no issues at all. Relatively new Dell Latitude 7390. Susan Bradley says “at least 2004,” so 20H2 should be OK.

Reply | Quote

I’m on 20H2 for all except 1 computer on 1909 which is my primary computer. Upgrading to either 2004 or 20H2 on that machine (Lenovo Yoga C-930) creates an Outlook problem with Outlook continually locking up and a password problem which creates an unworkable operating environment.

I will eventually do a complete rebuild when 20H2 stabilizes but I have way too many apps to reinstall to take the machine out of service for a week or more to get that done right now.

A client had the same problems with her computer and waited too long to do a reversion so we had to replace the computer to get her effectively working. The new  one is on 20H2 and will be completed this week.

Reply | Quote

I set target release version to version 2004 some weeks ago…. when will it install on its own?

I have deferrals set to 21 and 180 days.

Reply | Quote

If TRV=2004, when Microsoft 2004 support is discontinued, then 20H2 will be installed on your system. Between now and end-of-life 2004, if you have TRV=2004, your operating system will remain at 2004.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

[Microfix]

You should only use TargetReleaseVersion or Feature Deferrals, but not both!
Create an image backup first.
recheck your settings in GP.
FU Deferral (which will be ignored anyway). + TargetReleaseVersion = 2004
you shouldn’t get Delta Updates (DU) or CU Previews
Quality deferrals = 0, and Auto updates – Enabled, value = 2

once done see if 2004 is offered, be prepared, and we advise to read this post by PKCano

If debian is good enough for NASA...

• This reply was modified 4 years, 1 month ago by Microfix. Reason: my notes updated

Reply | Quote

[Ken]

I also have the Conexant drivers: I guess must I uninstall them before installing 2004? Where do I find them to reinstall after?

Maybe I should just wait for 20H2 and avoid the problems with 2004?

• This reply was modified 4 years, 1 month ago by Ken.

Reply | Quote

[Microfix]

WU should provide them although I’m not 100% sure on that. anyone?
Edit: https://borncity.com/win/2021/01/25/workaround-for-windows-10-2004-20h2-conexant-audio-driver-problems/

If debian is good enough for NASA...

• This reply was modified 4 years, 1 month ago by Microfix. Reason: additional link for info

Reply | Quote

Re Conexant drivers: device manager also offres to check for updates. If they are updated does this resolve the problem?

Reply | Quote

See this thread. Especially #2318988 and #2326241.

Reply | Quote

[Ken]

the link you offer mentions some file names…. where do I find these?

 

The “file version” is this the same as the “driver version”?

• This reply was modified 4 years, 1 month ago by Ken.

Reply | Quote

Microfix wrote:

You should only use TargetReleaseVersion or Feature Deferrals, but not both! Create an image backup first. recheck your settings in GP. FU Deferral 0 or 1 + TargetReleaseVersion = 2004

This is really confusing, pls elaborate as we are also discussing over at AKB2000016:

Using Group Policy settings – first you say to not use both TRV and Feature [Update] Deferrals. Then you show to set FU [Feature Update] Deferral [to] 0 or 1 AND TRV to 2004.   Thus setting both.

Pls clarify as this is coming up over and over in various postings as we approach the switch to 2004. Some responses say choose only 1, others continue to say what you said above.  Which is it?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

my bad, fixed for more clarty.
If you have TRV set, deferral days will be ignored, so it could be any numerical value 🙂

If debian is good enough for NASA...

Reply | Quote

See #2337357.

Reply | Quote

PKCano,

I have WIN10 Home, currently with version 1909. I want to up to version 2004 and have the USB with 2004 ready (which you had previously told me to save!). The Forum references the Pro version which I do not have and cannot get at this time.

What is the “best procedure” to do this upgrade of versions?

Do I keep Metered ON? Do I keep Updates Paused?

I do know I will have to regedit and change the line to reflect version 2004.

I’m sure you will recognize me from your great prior assistance, which I could very much use again!

Thanks,
Gunny

Reply | Quote

The easiest way to upgrade to v2004 is using the TargetReleaseVersion instead of the ISO. To do this:
+ Set Metered connections to ON.
+ In an elevated Command prompt, run the second command in AKB2000016 Section 2 using 2004 instead of 1909. (You will not have to run the first command again, it is already set.)
+ Wait for Windows Update to scan on its own – it should offer you Feature Update v2004.
+ If there is anything else in the queue that you don’t want to install, use wushowhide to hide it and wait for WU to scan again and remove it from the queue.
+ When v2004 is the only thing there, turn Metered connections OFF and sit back and let ‘er rip.

Reply | Quote

[Ken]

You said “+ Wait for Windows Update to scan on its own – it should offer you Feature Update v2004.”…. how does WU scan if metered connections are on?

• This reply was modified 4 years, 1 month ago by Ken.

1 user thanked author for this post.

joltar

Reply | Quote

Metered connections doesn’t prevent WU from scanning.
It only meters/checks/stops the download.
It’s telling MS you have a data cap/limit (even if it’s not the truth), so not to bust your budget.

2 users thanked author for this post.

joltar, Ken

Reply | Quote

PKCano,

First, I thought using the USB I got for v2004 was the way?
I understand most of what you said except, after changing the second line to reflect v2004, “wait for WU to scan on its own”. Do I need Pause to be OFF? Do I do this process as if a normal monthly update? I definitely am missing a step or two here or else I am in idiot mode again.
A bit more help please.

Gunny

Reply | Quote

[CADesertRat]

My Plan, please tell me the ramifications.

I’m currently 1909 Pro 18363.1256 with GP set to Feature Updates 365, TRV set to 1909.

I have a USB saved from when the first advice came out to save one, it’s 2004 19041.450 and my plan is to change GP to Feature Updates 0, TRV to 2004 after disconnecting the internet and put the USB in and upgrade. After upgrading to 2004, I assume that I will need to run WU to catch up to current updates and hope for the best.

I don’t have WUShowhide to stop anything.

Thanks for any response.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

• This reply was modified 4 years, 1 month ago by CADesertRat.

Reply | Quote

If you have the Feature Deferral set in the GUI Windows Update\Advanced Settings, that will go away in v2004. There are no pulldowns in v2004.

Prior to doing anything, make these changes in WU settings:
+ In GP under Windows Update, set the “2” (notify download/install) if it is not already set).
+ In GP under Windows Update for Business Set the TRV to 2004 See #2286499) and Feature deferral to the settings shown in the second screenshot in #2275043, except using 0 or 1 instead of 365. The explanation is above the screenshot, but if you need further explanation see #2337357.
+ Set both of the deferral pulldowns in the GUI to 0 (zero). GP settings take priority

If you use the ISO, you should disconnect from the Internet during the install.
You will need to update from Build .450 to .746 afterward using whatever your normal methods are.

Actually, the easiest way, with TRV set, is just to wait and let WU offer it to you. It will automatically put you at .746 – and the settings that it may change will be the same in either case.

3 users thanked author for this post.

ceruleandaze, Save_Us_from_MS, CADesertRat

Reply | Quote

I decided to start on my HP laptop after turning off the wireless.

1- I already had the “2” setting

2- I set Feature Deferral to 0

3- I changed TRV to 2004

I also ran Resume updates to see the error since it had no internet.

5- I am now in the process of installing the USB of .450

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

So, how’d it go? Smooth and easy or were there a few hiccups along the way?

Reply | Quote

It went ok. I did another computer today and just checked for updates after changing GP etc and it went ok also. My internet is slow so it took a long time but no problems.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I did another desktop this morning using the USB stick like I did with the laptop and I think it’s much faster than going the WU way that I did the last desktop yesterday since 2004 was already on the computer so all I had to do was check for updates to get to 19041.746. My internet isn’t very fast so it’s faster for me to install by USB first.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

^^^^^ in case anyone missed this make sure you read PK’s last sentence^^^^^

Actually, the easiest way, with  TargetReleaseVersion set, is just to wait and let WU offer it to you. It will automatically put you at .746 – and the settings that it may change will be the same in either case.

 

 

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan Bradley wrote:

Prior to doing anything, make these changes in WU settings:

One of the recommendations is to disable one’s A/V and to let Defender take over during the update process. Does one disable the A/V with some setting in Win10? Or does one disable the A/V within the A/V itself? If it’s at some screen in Win10, where is it?

Reply | Quote

If you go to Settings > Update & Security > Windows Security > Virus & threat protection; on the right hand side should be a link ‘Manage providers’ – click on that and then you will see something similar to the image attached.

Most likely you’ll have to disable your AV within the program itself rather than Windows do it for you via a setting. As an example, I use Avast and this can be done via right-clicking on the icon in the notification tray.

I’d do this while disconnected from the internet, and then you can enable Windows Defender Antivirus so you are protected for once you go back online after the update.

Hope this helps.

 

1 user thanked author for this post.

b

Reply | Quote

Coldheart9020 wrote:

If you go to Settings > Update & Security > Windows Security > Virus & threat protection …;

McAfee is my main A/V. I see where I can go into McAfee and turn Real-Time Scanning off. I can also turn the McAfee Firewall off, as well.

At “Virus & threat protection,” at the bottom of the screen I have “Windows Defender Antivirus options” | “Periodic Scanning” set to ON. The directions say “Your can keep using your current provider and have Defender A/V periodically scan for threats”. Since I am turning McAfee OFF, do I turn Windows Defender Periodic scanning OFF, too?

At “Virus & threat protection,” I have to scroll down to the lower-left hand corner of the screen, where I see a gear and the label “Settings”. That is where I find “Security providers” and the link to “Manage providers”. My screen looks the same as yours, except that it says McAfee, instead of Avast and it has some more information about the Firewall. See attachment for a screenshot of it.

For this screenshot, I haven’t turned McAfee Real-Time Scanning or McAfee Firewall to OFF yet. So, when I turn one or both OFF, will this screen says that Windows Defender A/V is turned ON (and that Windows Firewall in ON)? Or do I have to do something else to turn each of these ON)??

Or is Windows Defender A/V (and Firewall) automatically ON, since I turned McAfee A/V (and Firewall) OFF?

Is there any “power down-power up” or RESTART needed, to get these changes effectively in place?

Reply | Quote

Okay, probably the simplest thing to do – when you are ready to update – is perform the update by either ISO or Windows Update. If there is a problem, the update will not be performed.

If, however there are compatibility issues regarding McAfee (I am assuming the AV and firewall are part of the same installation?) then try disabling them and then updating.

If there is still an issue, just uninstall them altogether, reboot and then try again to update. There shouldn’t be however, as there are no documented known issues for v2004 regarding it.

If you are updating by ISO, you can disconnect from the internet and stay disconnected until you reinstall McAfee AV and firewall once on v2004.

Regarding Windows Defender’s periodic scanning: there is no harm in having this enabled while having a third-party AV installed. Since the real-time components of Defender are not enabled it will not conflict with your AV.

In fact Windows Security will not even let you enable the real-time protection for Windows Defender Antivirus or Windows Firewall while other AV/firewall software is installed, so it’s a case of ‘one or the other’.

Like I said, if you are ready to go to v2004, the simplest thing is to try updating. If you have TRV set to 2004 in Group Policy (and WU deferral settings for Feature updates set to 0 days, then you can stay connected to the internet and you will get v2004.

If by ISO, disconnect from the internet, perform the update and then check all settings before reconnecting to the internet and installing necessary Quality updates from WU.

Hope this helps 🙂

Reply | Quote

Coldheart9020 wrote:

In fact Windows Security will not even let you enable the real-time protection for Windows Defender Antivirus or Windows Firewall while other AV/firewall software is installed, so it’s a case of ‘one or the other’.

I am not going to use an ISO. I will be updating via WU by changing TRV to 2004, keeping GP ‘2’ (notify download/install), setting GP Feature Deferral to 1, and setting the 1909 GUI deferral pull downs to 0.

I don’t want to be without an A/V at all. I will be turning off McAfee (by changing settings in McAfee to turn off Real-Time Scanning and its Firewall — both part of McAfee). I don’t think it will be necessary to uninstall McAfee altogether, since I have changed its settings within to OFF.) So, this at this point, I think I will have ‘none’ and not ‘one of the other’. How do I get Windows Defender to turn ON so that I will have an A/V functioning. Or will it turn ON automatically, since McAfee has been turned OFF?

In other words, I want to have Windows Defender ON since there needs to be an A/V functioning at all times. Do I have to do something to make it turn ON? Or will it turn ON by itself?

Maybe I RESTART after turning OFF McAfee, so that after restarting, Windows Defender kicks in?

Reply | Quote

I have been deferring updates for quite a while. I finally updated my Lenovo laptop windows 10 pro to 1909 within the last 24-48 hrs. Following what I’ve read I went to the target release version and set it to 2004. That is the only change I made. I applied and said OK to the change. Then I checked for Windows updates and got an error message.   After going through various basic fixes for balky windows updates that I found on various Windows websites I was still getting an error. I decided to go back into the target release version and I removed 2004 and then applied and save the change. And I went back to Windows updates and the Windows update worked. But it’s loading 20H2 not 2004. So I paused my updates again until the patch lady says 20H2 is OK. 😀

Reply | Quote

Put in 2004 and the let it sit.  Don’t do a check for updates, just let it do it’s thing.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

By letting it do its own thing, I am assuming that the next time I do a monthly patch, it will do its own thing through what I allow to be patched!?!? Will that be “Feature Update” or will it actually say the v number?

Reply | Quote

I would let it sit.  In several hours go back to that windows update section and it should offer up 2004 in that box.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan, I appreciate your response however, I am a bit thick and do not quite understand your last sentence, so let me be more direct.

Even as a WIN 10 Home user, I understand how to change the Target Version to 2004. After that, I think what I should do is wait for the next patch (January’s) to go to Defcon 4, run the patching process using the wushowhide method and in that process look for the version 2004 update and accept it. If that is correct, then what I do not know is whether the version 2004 update is shown as a version 2004 update or as merely a Feature Update?

Thanks,
Gunny

Reply | Quote

Don’t worry, if you are offered v2004, it will be very clear that is a Feature Update, not a monthly Cumulative Update.

The monthly update would be 2021-02 Cumulative Update (for Feb).

Reply | Quote

OK then!
The next update would be the January 2021 when the Defcon status changes from Defcon 2, as it is now.
To me, that means that when the January updates are “cleared”, I should be ready for the version change (Feature Update) and go for it, and, I will be using the wushowhide method!
If I am wrong in this, let me know. Otherwise, I expect to post my successful first time version update!
Again, many thanks to both you and Susan for all the help.

Gunny

Reply | Quote

TygerDad wrote:

but not 1909 to 2004

1909 EOL for home users is 2021-05-11 so Microsoft will force updates to 2004 way before EOL date.

Reply | Quote

Ken wrote:

OK, now I understand, did it. Now should I resume updates or just wait until just befopre my pause ends (2/6) at which time I’ll do the metered connecting thing.?

I often wonder, what do the millions of Windows users do without your advice? Just hope for the best?

Reply | Quote

Most of them are clueless on how to do these type of things and have no real clue that places like Ask Woody exist.  They leave their computers as originally configured and consult with repair services when things go wrong.

Reply | Quote

With all of the posturing for when to Allow 2004 several here have spoken of 20H2 Upgrades (me from 1909) with No Issues, and I haven’t seen a real Disaster Post from having done so. (Me) Uninstalling the Conexant Driver (Not Deleting) was a key, with 20H2 apparently replacing it with the Same Driver.

For the Basic system users ((ie) Ethernet from a wall) … What are the “current” reasons for Not Clk’ing – Update Now – from the 20H2 Dnload page – as long as Images are made prior? Life is simpler when you’re as far as you can go with Feature updates. Miles of cable and stacked modems, another story….

Reply | Quote

As I recently promised, I upgraded to v2004 successfully and with no problems.All is working well.

This was my first time to upgrade and I thank all for the help I received.

Gunny

1 user thanked author for this post.

PKCano

Reply | Quote

I was watching the thread and was happy to see it worked out for you.

Reply | Quote

If you have Fast Startup turned on, when you  shutdown/turn on, the system saves some information so that you have a faster startup. The part that’s saved is still the same as the last time the computer was on. So the computer doesn’t actually shutdown all the way.

It doesn’t do that if you restart.

1 user thanked author for this post.

WCHS

Reply | Quote

This probably explains the shutdown error msgs that I rec’d during a turn off/turn on (not restart). I have not noticed lags in startup with Fast Start disabled although I have not timed it to the second.

Reply | Quote

b wrote:

It doesn’t do that if you restart.

Could you read #2338562, which is a question about #2338179 (and not #2338554, my bad).

Paul T says at #2338565 that “as far as Windows is concerned, there is no difference” (between power down/power up vs RESTART). I am not sure if this means “It makes no difference what you do” OR “there is no difference between power down/power up and RESTART.” I read here that there IS a difference (i.e., power down/power up is not the same thing as RESTART).

So, in #2338179, does “Reboot” mean “You can either power down/power up or RESTART–makes no difference which you do”?

I ask because the prior step is to use wushowhide to hide the updates you don’t want. It seems to me that after that, you’d want to start up clean (and power down/power up wouldn’t do that).

Reply | Quote

There’s a BIG difference as far as Windows is concerned between shutdown/powerup (with default fast startup) and restart. Only restart provides a completely fresh start (as evidenced by “Up time” in Task Manager).

AKB2000013 says, “+ Restart the computer (not shutdown/bootup)”.

1 user thanked author for this post.

WCHS

Reply | Quote

Sorry, I was wrong. From the MS site:

Full shutdown only occurs when you restart a computer or when other event causes the computer to process a full shutdown.

In order to make sure Windows updates that require pending operations being installed properly, you have to restart your computer to complete the installation.

cheers, Paul

2 users thanked author for this post.

b, WCHS

Reply | Quote

WCHS wrote:

setting GP Feature Deferral to 1, and setting the 1909 GUI deferral pull downs to 0.

Why would you set the Feature deferral to 1? And do you mean quality updates in the deferral pulldowns? I’m assuming so because it doesn’t make sense otherwise.

With the ‘Select the target Feature Update version’ set to the version you wish to update to/stay on, there’s no need to configure the other things in GP under Windows Update for Business.

You already have GP set to ‘2 – Notify for download and auto install’ so you don’t need to worry about Quality update settings either; they can stay not configured in GP.

As for enabling Windows Defender AV and Firewall, once you disable McAfee you may get a notification that you have no AV/firewall. If not, just go into Windows Security > Virus & threat protection > Virus & threat protection settings and there you can toggle real-time protection. It won’t allow you to do so while another AV is active (i.e. is providing real-time protection). That is what I meant by ‘one or the other’: you can’t have two AV or firewall programs running at once. So it’s one (McAfee) or the other (Windows).

Same for enabling Windows Firewall; you’ll find the menu in Windows Security. Again you can’t enable it while another third-party firewall program is running.

1 user thanked author for this post.

WCHS

Reply | Quote

Coldheart9020 wrote:

Why would you set the Feature deferral to 1?

Please see #2337863 and a few posts before and after that one. There’s been an ongoing discussion of why.

The short answer is: because I want to prevent Cumulative Previews from showing up, not even with a Download button.

Thanks for the info on Enabling Windows Defender and Firewall (after McAfee is turned off). Do I need to do a RESTART afterwards? Or do these two actions (turning off McAfee and enabling Windows Defender) kick in immediately?

Reply | Quote

Oh, I see. I just hide them in wushowhide when they appear. As long as it works for you, that’s the main thing 🙂

1 user thanked author for this post.

WCHS

Reply | Quote

Coldheart9020 wrote:

Oh, I see…..

I edited while you replied. I added a question — about RESTARTing or not.

Reply | Quote

WCHS wrote:

Do I need to do a RESTART afterwards? Or do these two actions (turning off McAfee and enabling Windows Defender) kick in immediately?

I’m not sure if it’s needed, but it wouldn’t hurt. Simply disabling McAfee AV and firewall protection should be enough. I just did a test with my Avast AV by disabling all shields and instantly I got the following notification:

However I was still unable to enable real-time protection in Windows Defender Antivirus. It may differ for McAfee though, I’m not sure. Disabling the AV shields in McAfee may work, before or after reboot, you’ll have to see.

For the firewall, I briefly disabled ZoneAlarm’s shields and got a similar notification. I was then able to enable Windows Firewall from the ‘Security at a glance’ main screen of Windows Security.

 

1 user thanked author for this post.

WCHS

Reply | Quote

Coldheart9020 wrote:

As for enabling Windows Defender AV and Firewall, once you disable McAfee

I don’t disable my Kaspersky A/V during updates, I pause until restart. Defender is still off.

Reply | Quote

I’ve not yet made any Feature updates; I came to Windows 10 v1909 a year ago from Windows 7. In a few months’ time around late April I’ll consider whether 2004 or 20H2 is most viable – if I can skip 2004 altogether I’ll be doing that and go straight to 20H2, but we’ll have to see.

Either way, when the time comes I’ll only suspend my Avast and ZoneAlarm if there’s an issue with the update.

1 user thanked author for this post.

WCHS

Reply | Quote

Coldheart9020 wrote:

In a few months’ time around late April I’ll consider whether 2004 or 20H2 is most viable –

Thanks for your thoughts on this. I want to wait until at least the magic date of Feb 12, which is when the IRS portal opens for filing 2020 taxes. I don’t want to be without a working computer when this date arrives, should updating to 2004 prove to be a problem.

Reply | Quote

Is it still recommended procedure to disconnect from the internet after Windows Updater has downloaded and installed ver 2004, and before Restarting your computer?

So that you can check on all your settings (including the new Group Policy settings – TRV, etc) before reconnecting to the internet.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I updated yesterday from 1909 to 2004 (pro)  without disconnecting although I do not know if that is recommended.  I made sure that the queue was cleared except for the 2004 update file. All of my group policy settings carried over such as TRV, 3rd party driver setting, etc.

However, other settings/configurations were not such as system restore had to be reset/restarted; disabled fast startup again, and a couple of others. Since I already have a 2004 pc here, it was easier and I had made a note of the system changes I had made along the way.

The update went well; took about 1 1/2 hrs, – could have reduced time, but I let it sit awhile before restarting  that may not have been necessary.

After the update to 2004, a .net patch from October (KB4578968) and the adobe remover patch (KB4580325) were offered which I installed today.

The only problem that I see is the multitude of Event 642 ESENT warnings in Event Viewer that were not present in 1909. But they have been there on my other 2004 pc for months and have presented no problems. Apparently no easy fix for that issue.

Hope all goes well.

1 user thanked author for this post.

jburk07

Reply | Quote

[Alex5723]

Tex265 wrote:

Is it still recommended procedure to disconnect from the internet after Windows Updater has downloaded and installed ver 2004, and before Restarting your computer?

Disconnecting from the Internet is recommended when installing clean install or from ISO.
Upgrading via Windows Updates doesn’t require Internet disconnecting.

• This reply was modified 4 years, 1 month ago by Alex5723.

Reply | Quote

Why would Feature Updating to ver 2004 be any different than updating from the prior versions wherein PK Cano always recommended we disconnect from the internet and recheck all out settings that require/prevent Microsoft from automatically installing updates upon ReStarts?

Not a challenge question, just don’t need anything additional unexpectedly.

Perhaps I should ask, Is there any problem if I disconnect from the internet after Windows Updater downloads and installs version 2004, then Restart, then double check all my settings, then reconnect to the internet?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Disconnect is for the ISO upgrade method only.
If you want to disconnect for any other upgrade – post download – it’s up to you.

cheers, Paul

Reply | Quote

I am running Windows 10 Pro, 64 bit.  Per Susan’s recommendation I am ready to move from 1909 to version 2004.  I followed all the advice and set the targeted release version as 2004.  When I run wushowhide it shows that 2004 is available to download plus some Office 2010 updates.  So what do I do now?  Do I click on check for updates to start the download – when we’ve all been told many times to never click on that?  Other than doing that I have no idea how to download and install version 2004.  I know this may sound dumb, but I am no expert on this.

 

Reply | Quote

If it is visible in wushowhide it should be visible in Windows Update.
Select it for install from Windows Update – do the Office updates after 2004.

cheers, Paul

1 user thanked author for this post.

BobbyS

Reply | Quote

[hms]

Same happened in my update to 2004. The 2004 Update file showed up first in wushwhide as an update that could be hidden. It was not shown in the normal Windows update window. I turned off the pc for the day. I did not check it in wushowhide. The next day the update file showed up in the normal Windows update window. From that window I did the install. Why did it first show up in wushowhide? I have no idea but it did.

• This reply was modified 4 years, 1 month ago by hms.

1 user thanked author for this post.

BobbyS

Reply | Quote

hms wrote:

Why did it first show up in wushowhide? I have no idea but it did.

Wushowhide is dynamic – it always knows what’s waiting in the WU queue.
WU is static – it doesn’t know what’s in the queue until it checks.
When does WU check?
1) It can check when you prompt it to “check updates”. This causes WU to download and install whatever it finds, which might not be a good idea, if there is something there that you wished you would have hidden. Or it might find something that you have hidden (it hasn’t updated itself yet, because the scheduled time for checking the queue hasn’t arrived yet, so it doesn’t know yet that it has been hidden).

2) Or it can check when it is scheduled to check. If it finds something there that has been unhidden beforehand, it will make it available on the WU screen then. And it won’t find anything that you have hidden beforehand.

2 users thanked author for this post.

BobbyS, hms

Reply | Quote

Paul T wrote:

it should be visible in Windows Update.

For it to be visible in Windows Update, you will probably have to wait until WU does its own automatic check of the queue (might be a wait as long as 18-24 hours).   When it does, it will find 2004 in the queue and you will see it on the WU screen.  And from there you can select for install.

This always happens when you unhide an update. You won’t see it immediately on the WU screen, unless WU is, fortuitously, scheduled soon after to do an automatic check of the queue.

1 user thanked author for this post.

BobbyS

Reply | Quote

Relevant to all Feature Upgraders …. Can someone Confirm IF Windows Auto-Deletes (in my case) 33 GB of — Windows.old — in 30 days, 15 days, ?? AND, IF you’ve been fine for 2.5 weeks and just want to clear it out, What Happens in Disk Cleanup when you Clk “Clean up system files”? Is THAT Win.old ?? Do you see something first – or it just does what it does? There is No Box showing anything with GB of data. & Is there Another or Better Delete method for Win.old ??

Thanks as always. ( With Images … You basic Home system guys ought to go 20H2 and be done with it.)

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

Windows removes Windows.old after 10 days. It gives you that time to roll back to your previous version if you have problems.

If you want to remove it before, you can RIGHT-CLICK on Disk Cleanup and run as Administrator. Be careful what you delete here. You can delete files from “Downloaded Program Files” but if you delete files from “Downloads” (without Program Files), that is your Downloads Folder.

1 user thanked author for this post.

CraigS26

Reply | Quote

Windows.old appears in Disk Cleanup System Files as “Previous Windows Installation(s)” (which is unchecked by default):

How to delete the Windows.old folder on Windows 10

Downloads doesn’t appear in Disk Cleanup on versions 2004/20H2 (only 1809, 1903, 1909):

Microsoft will remove option to clear Downloads folder using Disk Cleanup

1 user thanked author for this post.

CraigS26

Reply | Quote

My experience updating from 1909 (Win10 Pro) to 2004.

I had an ISO of 2004 (previously burnt to DVD from MS website) which I tried to run from my desktop and it failed the installation with the following error message: “0x800F0830-0X20003 The installation failed in the SAFE_OS phase with an error during INSTALL_UPDATES operation”. Tried several times, no joy each time.

Changed the TargetReleaseVersion setting to 2004 a couple of weeks ago and finally when updating my deferred January updates v2004 was offered and installed w/o issue.

Anybody care to comment or speculate on why the update failed using the ISO?

Thank you Susan for all your tips.

Win10 Pro 2004 / Custom Build Desktop

Reply | Quote

The update from the ISO may have failed if you still had the TRV set to 1909 instead of 2004 when you tried the update.

Just a thought.

Reply | Quote

Nope, I tried it both ways.

Reply | Quote

My guess, the ISO was older bits, the newer WU has a fix in it.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Could be, it was an older burn. Back when Woody suggested to secure a copy before 20H2 came to be.

Win10 Pro 2004 / Custom Build Desktop

Reply | Quote

I have a Win10 PC bought in November 2019. Unfortunately it sat unused until now. I finally am going through initial setup.

This PC came with Windows 10 Pro 1909, Build 18363. It has not yet been updated nor connected online.

I’m new to Win10, GPEdit, wushowhide, etc., . . .

I have followed PKCano’s recommendations for 1909 Pro in AKB2000016 Section 4:

GUI – Feature Updates Deferral = 365, Quality Updates Deferral = 0

GPEdit – Configure Automatic Updates = Enabled, Configure Automatic Updating = 2, also Do not include drivers with Windows Updates = Enabled

I would prefer to update to 2004 at this time, not 20H2. I do not have Conexant audio drivers. I assume that if I proceed to update now with the settings shown above Windows Update will show me the 20H2 Feature Upgrade and the February Cumulative Update for 20H2 and they will sit there until I click to Download them. Correct?

To get 2004 instead of accepting 20H2 can I (should I) use Susan’s .reg file to add the Group Policy TRV settings to my 1909 Pro Registry as described here?

https://www.askwoody.com/2021/tasks-for-the-weekend-january-30-2021/

I assume a current 2004 Feature Update will include all the 2004 Cumulative Updates I’ve missed so far. Correct?

Should I expect a lot of additional updates because this will be the first update for this PC since Windows was installed in November 2019?

Now that Patch Tuesday has arrived should I hold off updating until we get Susan’s all clear for February? Or should I proceed and use wushowhide to hide February updates?

Thanks!

 

Reply | Quote

Use the reg files to set TRV to 2004, than set both deferral pulldowns in the GUI to 0.

You will need to change the Group Policy settings when you upgrade to 2004, as the pulldown switches will no longer be available in the GUI.
See Section 5 of AKB2000016 for instructions.

1 user thanked author for this post.

opti1

Reply | Quote

Your new PC, for reference: #2008763

cheers, Paul

Reply | Quote

LOL. Yeah, that seems like a lifetime ago, before COVID and shutdowns and other life stuff happens kicked in. Hard to believe I’m just now actually starting to get this PC up and running.

Thanks, by the way, for your input across posts. That goes for others too – PKCano, Susan, Woody of course, Alex, Tex, and others I can’t pull out of my head this early in the morning. Thanks all.

Reply | Quote

[Alex5723]

opti1 wrote:

To get 2004 instead of accepting 20H2 can I (should I) use Susan’s .reg file to add the Group Policy TRV settings to my 1909 Pro Registry as described here?

Yes. In 1909 use the .reg to set TVR to 2004

You will get updated version of 2004, probably including Jan. 2021 updates.

• This reply was modified 4 years, 1 month ago by Alex5723.
• This reply was modified 4 years, 1 month ago by Alex5723.

1 user thanked author for this post.

opti1

Reply | Quote

Since the OP already has 1909 with the Windows Update Advanced GUI pull downs, why not just set the Feature Update deferral days to say 250 days and let version 2004 come down automatically at the next Update check vs futzing with a registry entry?

Then allow the 2004 installation, disconnect from the internet, make the Group Policy settings referenced below (since the pull downs are gone in version 2004) including setting TRV to 2004 in the updated Group Policies, then reconnect to the internet – and done.

PKCano wrote:

You will need to change the Group Policy settings when you upgrade to 2004, as the pulldown switches will no longer be available in the GUI. See Section 5 of AKB2000016 for instructions.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I am currently running Windows 10 Pro ver 1909 on an older Lenovo T520i laptop. Works OK. I just got offered by Windows update the upgrade to ver 2004 for the T520i.

I have not yet tried to install it.

I did a recent (a couple of days ago) Macrium Reflect backup of the boot drive on the T520i.

Should I try installing the ver. 2004 upgrade to Windows 10 Pro on the T520i?

I have Ver. 2004 installed on my Lenovo W530 and on my ASUS TUF laptop, (both running Windows 10 Pro) (just bought the ASUS in Sept 2020). Everything works fine on those two machines.

Any cautions or recommendations?

WSthesquire

Reply | Quote

You have been offered the update, you have a backup, go for it!
The only thing you may want to do is wait another few days to here if there are any major issues with the Feb patches, because they will be included in the update.

cheers, Paul

Reply | Quote

Regarding Macrium Reflect Free:

I made a full backup of my 1909 hard disk onto my Western USB hard drive. I also have a separate Rescue Media USB stick made while on version 1909.  If the 2004 Update had problems and I had to use the Rescue Media USB stick to boot into the backup, would it work since it was made under 1909?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

your Macrium usb rescue media will boot to where it can restore you image(s). If you haven’t already done so, create a 2004 image and it will be available for restore also. Test your rescue media to ensure your boot sequence (on BIOS/EUFI) will look at usb stick before your regular boot drive (probably C:)

Reply | Quote

Rescue media boots independently of any installed OS.

cheers, Paul

Reply | Quote