MS-DEFCON 4 – Make sure January updates are installed

[Susan Bradley]

It’s time to make sure January updates are installed. More details are in the AskWoody Plus newsletter out  tonight/tomorrow (sign up for it here). I’
[See the full post at: MS-DEFCON 4 – Make sure January updates are installed]

Susan Bradley Patch Lady

5 users thanked author for this post.

jburk07, rexr, rgmarsicek, geekdom, abbodi86

Reply | Quote

[PKCano]

I have updated AKB2000016 to reflect the TargetReleaseVersion (TRV) settings and methods discussed in Tasks for the weekend – January 30, 2021.
Section 1 concerns general information on Win10 settings.
Section 2 concerns making the settings for TRV in Win10 Home.
Sections 3 & 5 concern making the settings for TRV in Win10 Pro.

Links have been added for the instructional video that Susan made and to the downloaded .reg files

2 users thanked author for this post.

MrToad28, jburk07

Reply | Quote

[anonymous]

from the main blog:

I’m recommending that Win10 Home and Pro users move to version 2004 (or 20H2) if you haven’t already done so.  Remember you can set the Targetfeaturerelease setting and make sure you only get to the version you want.

Susan, I presume you mean (TRV) TargetReleaseVersion, it gets confusing when names for things are changed.

Reply | Quote

[Susan Bradley]

My bad, fixed!

Susan Bradley Patch Lady

Reply | Quote

[Bob99]

I just made the “jump” from 2004 to 20H2, and the preference in GPEdit is listed as “Select the target Feature Update version” and it’s still one of the items under the Windows Update for Business folder.

I guess just another case of “6 of one, half dozen of another”.  😉

Reply | Quote

[DriftyDonN]

Acronyms are no longer PC  🙁

Reply | Quote

[anonymous]

We are still waiting for the C/D patch for 20H2, maybe at the beginning of this week it will come out and will be patch A.

Reply | Quote

[Noel Carboni]

All’s well so far…

-Noel

Attachments:

You must be logged in to access attached files.

1 user thanked author for this post.

jburk07

Reply | Quote

[davinci953]

What’s the status with KB4535680? I have it hidden for now.

Reply | Quote

[TJ]

Upgraded from 1909 to Version 2004 Build 19041.746 succesfully (but it took h-o-u-r-s) and all seems o.k., apart from Windows putting a Cortana shortcut on the Taskbar and deleting some shortcuts from the Start Menu.

1 user thanked author for this post.

jburk07

Reply | Quote

[anonymous]

Alright, since you said its cool to move from 1909 or 2004-Then I can install the new version this week then. Also what do you mean by  Targetfeaturerelease setting? You mean in windows update or something?

Reply | Quote

[Paul T]

TargetReleaseVersion is the correct term.

To get the update, set TRV and wait for Windows to offer the update, then install. It may take a day or two for the update to be offered.

cheers, Paul

Reply | Quote

[anonymous]

How do I set TRV? Doesn’t windows update offer the 2004 version update or the update/upgrade assistant? I’m not savy in register code or stuff.

Reply | Quote

[Susan Bradley]

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

Susan Bradley Patch Lady

Reply | Quote

[anonymous]

Susan? Is there an easier way? I’m not savvy in registry editor nor ever used it and I don’t wanna mess up my computer.

Reply | Quote

[anonymous]

Wait how do you get the 2004 update safely? For those windows home and easy way to install it? Is it on windows update or do I have to download a safe copy of it? Or check the upgrade assistant?

Reply | Quote

[PKCano]

See #2339089 above and  Tasks for the weekend – January 30, 2021

Reply | Quote

[gary]

How do I upgrade from  W-10 Home version 1909 to W-10 Pro version 2004?  Appreciate a detailed guideline.  Thanks

Reply | Quote

[Paul T]

You need an upgrade license to go from Home to Pro, at a cost of around $100.

Stick to Home and use TRV to tell Windows what to update.

cheers, Paul

Reply | Quote

[anonymous]

I got error 0xc1900401 for the January cumulative update for 2004. Do you know what it means?

Reply | Quote

[b]

A frequently observed result code is 0xC1900101. … 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present.

Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.

Resolution procedures – 0xC1900101

Reply | Quote

[anonymous]

Is 0xc1900401 the same as 0xC1900101?

Reply | Quote

[b]

No, I apologize; that was my mistake.

But it is mentioned near the bottom of that same page, although more obscure:

0XC1900401
MOSETUP_E_UA_NO_PACKAGES_TO_DOWNLOAD
No packages to be downloaded.

A couple of members who had that error in previous months found that updates had in fact been completed, and the next check for updates said, “You’re up to date”. So perhaps a temporary glitch?

Reply | Quote

[anonymous]

Indeed I seem to have the latest build. What’s weird is it doesn’t show up in Update History.

1 user thanked author for this post.

b

Reply | Quote

[James Bond 007]

Is this recommendation for Windows 8.1 as well as Windows 10?

I don’t use Windows 10 at this time and I don’t care for it one bit. My own systems still run Windows 7 and Windows 8.1 (I know Windows 7 is out of support but so what? It still runs well for me.). For my Windows 8.1 systems I just patched up to December 2020 level at the beginning of January and I am not going to patch them this month as there seems to be no urgent security issues. I will wait a few months before patching again.

I have been working like this for the past 3 years (2018-2020) and have no issues.

Hope for the best. Prepare for the worst.

Reply | Quote

[Susan Bradley]

I install updates the same month as they come out.  I personally feel that keeping up to date (after a reasonable delay to watch for issues) ensures that the system remains healthy.  I’ve personally had issues on machines that haven’t updated in a while.

Susan Bradley Patch Lady

Reply | Quote

[Berserker79]

Windows 10 1909 Home here. Everything in working order (as far as I can tell) after installing the following patches through WU:
– KB4598229 – 2021-01 Cumulative update for Version 1909
– KB890830 – Windows Malicious Software Removal Tool x64 v5.85
– KB4486759/KB4486762/KB4493176/KB4486764 – Office 2013 patches

Manually installed KB4586878 (January 12, 2021 .NET Cumulative update) since no longer offered through WU due to its replacement by KB4598301 (January 26, 2021 .NET Cumulative Update Preview). Also, I skipped KB4535680 at this time.

BTW, since Susan has green-lighted both 2004 and 20H2, I’m planning to move from 1909 directly to 20H2 sometime before 1909 reaches EOL: any reason why I should prefer 2004 rather than going directly to 20H2? Also, I’m planning to update with an ISO file (just grabbed a 20H2 ISO using the MediaCreationTool) or should I let 20H2 through WU?

3 users thanked author for this post.

WSRJT97355, jburk07, Coldheart9020

Reply | Quote

[PKCano]

20H2 through Windows Update will probably give you an up-to-date Build.
If you use the ISO, you will get the Build that was current when the ISO was made and you will have to update it to the current. That’s basically two update hassles for the price of one.

3 users thanked author for this post.

WSRJT97355, Berserker79, jburk07

Reply | Quote

[Berserker79]

Thank you PKCano, the less hassles the better when we are talking about updating Windows. Still, it’s going to feel vaguely strange to get a Feature Update through WU after using a ISO for a while. 🙂

Reply | Quote

[Ian Ordish]

Can I ask how you were able to skip the kb4535680 update.  This keeps failing to install on a machine that I working on. It’s running Windows 10 Home version 1909.
Thanks

Reply | Quote

[PKCano]

Download wushowhide.diagcab, place it on your desktop, run it (Advanced, uncheck make changes automatically), and hide the update.

1 user thanked author for this post.

Ian Ordish

Reply | Quote

[Berserker79]

Apologies, I did not get a notification for your reply and didn’t read the question until today. Anyway, as already answered by PKCano below, wushowhide is the way to go to hide and skip kb4535680 (as well as any other undesired update).

Reply | Quote

[Matador]

Yes, a very important tool for anyone who wants control over the update process

Reply | Quote

[TJ]

After having upgraded to 2004 last night and all seemed well, Windows Update showed 3 updates in its queue, among which KB4023057. I had it hidden in 1909, but to no avail, so I had to hide it again and clear the queue, and install the .NET and Flash update.

But wushowhide also showed updates from third parties, that didn’t show up in the WU-queue. (WU is set not to download drivers.)
3 of them are Intel system drivers, 1 is an Intel ethernet connection driver and 1 Realtek audio driver.
Are these Intel system drivers the microcode ones, so should they be avoided?

Reply | Quote

[PKCano]

TJ wrote:

After having upgraded to 2004 last night and all seemed well, Windows Update showed 3 updates in its queue, among which KB4023057. I had it hidden in 1909, but to no avail, so I had to hide it again

KB4023057 has been reissued multiple times. Each time it is released the metadata (at least) is changed. Even though it has the same KB number, it is treated like a new release, so you have to hide it AGAIN each time.

TJ wrote:

Are these Intel system drivers the microcode ones, so should they be avoided?

Since you have not mentioned KB numbers – we have no way to answer your question.
If they are drivers, we do not recommend getting them from MS.
If they are Microcode, you can find out by putting the numerical value of the KN number  in the MS Update Catalog search box and reading the description, then clicking on the title and “More Information” in the box that pops up.

2 users thanked author for this post.

Coldheart9020, TJ

Reply | Quote

[TJ]

They are all drivers without any KB-number. See attachment.
I can only hover over each one in WUMT to see additional info.

Attachments:

You must be logged in to access attached files.

Reply | Quote

[geekdom]

Get Intel drivers here:
https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html

On Hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 20H2.19042.804 x64 i5-9400 RAM16GB HDD Firefox86.0 WindowsDefender TRV=20H2 WuMgr

2 users thanked author for this post.

Perq, TJ

Reply | Quote

[TJ]

Thanks, I know the tool but it was giving incorrect drivers the last few months. I’ll try it again.

Reply | Quote

[TJ]

The Intel DSA ran good now and says all rivers are up to date.

@PKCano I hid all the drivers now.

Reply | Quote

[davinci953]

davinci953 wrote:

What’s the status with KB4535680? I have it hidden for now.

I saw the current guidance for this patch in this week’s newsletter. Thanks.

Reply | Quote

[geekdom]

Beta Test
February 1, 2021

• Created backup: system image; files and folders
• Changed TRV in registry from 2004 to 20H2
• Installed Feature Update 20H2 using WuMgr
• Rebooted
• No errors during installation or after reboot

On Hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 20H2.19042.804 x64 i5-9400 RAM16GB HDD Firefox86.0 WindowsDefender TRV=20H2 WuMgr

1 user thanked author for this post.

jburk07

Reply | Quote

[Sproots]

Once I change TargetReleaseVersion, I’m moving 1909 to 2004, what do you do to kick the update into the queue?

I’ve restarted and shut-down restart a few times but still hasn’t run its own system check.

Should I “check for updates” which I do not normally do per PcKano settings?

Should I just wait until tomorrow when the system will do its normal daily check for updates?

Reply | Quote

[Alex5723]

Just wait.

Reply | Quote

[Charlie]

Susan, you say to update MS Office along with the other Windows updates.  But all of the Office updates are still marked “Deferred” as of this time at date in the Master Patch List.  Shall I go ahead and update my Office 2010 now or wait?

Reply | Quote

[b]

The Master Patch List updated yesterday says “Install” for all Office versions.

1 user thanked author for this post.

Microfix

Reply | Quote

[Charlie]

I just went there again just now and the Jan. 12th updates are still noted as deferred in the install column.

• This reply was modified 3 weeks, 6 days ago by Charlie.

Reply | Quote

[b]

Please use the top set of links under

January 31 2021 — Update Status

not the older ones under

January 18, 2021 — Update Status

Reply | Quote

[Susan Bradley]

Note that I’m only going to be releasing a month of patches listing, not the individual spreadsheets like I did.  Thus look for the January 31st list.

Susan Bradley Patch Lady

2 users thanked author for this post.

rexr, Charlie

Reply | Quote

[DrBonzo]

@Charlie – FWIW I installed the 2010 Office updates on a Win 7 computer on Saturday night. Very fast installation and no issues.

KB4493186, 3143, 3181, and 3145. The last three in the list all begin with KB449.

3 users thanked author for this post.

SueW, jburk07, Charlie

Reply | Quote

[Charlie]

I installed mine on my Win 7 computer yesterday with no apparent problems.

3 users thanked author for this post.

SueW, DrBonzo, jburk07

Reply | Quote

[Coldheart9020]

TJ wrote:

Upgraded from 1909 to Version 2004 Build 19041.746 succesfully (but it took h-o-u-r-s)

Did you do it via Windows Update? From what I’ve read it’s much quicker by ISO, which makes sense.

I have an ISO of v2004 19041.450 waiting to go for when the time comes. 🙂

Reply | Quote

[JD]

January patches installed with no problems to report on Win 8.1 .  🙂 Skipped installing KB4535680 as recommended.

Installation Successful: Windows successfully installed the following update: 2021-01 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4598285)

Installation Successful: Windows successfully installed the following update: 2021-01 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 and Server 2012 R2 for x64 (KB4598502)

Group "A"- Win 8.1 x64
Win 10 ver. 20H2 x64
Win 10 Pro ver. 2004 x64

2 users thanked author for this post.

cbpoker, DrBonzo

Reply | Quote

[DrBonzo]

These are the exact same results I got last night on 2 Win 8.1 computers.

1 user thanked author for this post.

JD

Reply | Quote

[Michael Austin]

Yesterday I patched my desktop mothership with Microsoft’s required January Windows 10.x changes. Unlike most past patch changes, the required January patches now cause stupid, time-wasting problems. No recommended patches were installed.

After the required January patches, twice now at boot time, the Taskbar search box, the keyboard, and the Windows key all failed to work — until after a 2nd boot. I rebooted by right-mousing over the Windows key so I could then use the keyboard and Start Menu. Microsoft is pushing me and my clients further and farther away, into the willing hands of other OS publishers.

Finance, social and tech founder. Co-founder of a global, gamified, crowd-sourced ESG advertising platform, and managing director of new crowd sourced games, both in pre-release development. My planet-wide talk show for people craving new stories by which to live is Casual Saints.

• This reply was modified 3 weeks, 5 days ago by Michael Austin.
• This reply was modified 3 weeks, 5 days ago by Michael Austin.

Reply | Quote

[chilton]

I installed January updates this morning.

WU said it was downloading 2021-01 Cumulative Update KB4598242.

After it was applied I looked at update history and it wasn’t there so I looked at Installed Updates and saw it there but labeled as Security Update.

Cumulative updates for 10, 11 and 12/2020 are all listed in update history.

Is this to be expected for January cumulative updates?

If so what’s the reason for not including all cumulative updates in update history?

thanks.

Reply | Quote

[sheldon]

I see the January cumulative KB4598242 in update history.  Maybe it’s farther down the list on your system and you just missed it.

Reply | Quote

[chilton]

I didn’t miss it.  See attached.

I wouldn’t expect it to be but it’s not listed under any of the other categories.

It’s interesting that you’re seeing it where I expected to see it.

 

Attachments:

You must be logged in to access attached files.

Reply | Quote

[rexr]

Updated to Win10 20H2 19042.746 from .685, update took about 20 minutes and two auto-restarts for CU KB4598242. On a laptop and desktop. No problems (fingers crossed).
The Taskbar search box, keyboard, and Windows key work fine here.

MS says “You’re up to date.” They haven’t seen my honey-do list.

Driver Updates from MS is always blocked, i get drivers from the OEM.

Win10 Pro 20H2 19042.746
Backups with Macrium Reflect home edition

Reply | Quote

[EP]

Coldheart9020 wrote:

TJ wrote:

Upgraded from 1909 to Version 2004 Build 19041.746 succesfully (but it took h-o-u-r-s)

Did you do it via Windows Update? From what I’ve read it’s much quicker by ISO, which makes sense.

I have an ISO of v2004 19041.450 waiting to go for when the time comes. 🙂

@Coldheart9020

I created a v2004 ISO with build 19041.572 (Oct. 2020 KB4579311 update integrated) from this ESD install package that includes the certificates bugfix after upgrading via ISO method. did an ESD to ISO conversion with either esd decrypt-multi-release or esd decrypter wimlib script before running the v2004 upgrade install offline w/ no internet connection during the upgrade process.

the 2004 ISO with build 19041.450 does not include the defrag and lost certificates fixes, so create an updated ISO that has at least build 19041.572

• This reply was modified 3 weeks, 5 days ago by EP.
• This reply was modified 3 weeks, 5 days ago by EP.

Reply | Quote

[EP]

at long last Microsoft has finally released new preview updates for 2004/20H2 on Tuesday afternoon February 2:

KB4598299 .NET preview update
https://support.microsoft.com/help/4598299

KB4598291 cumulative preview update (build 19041/2.789)
https://support.microsoft.com/help/4598291

Reply | Quote

[Microfix]

Clean ‘full metal jacket’ installation 20H2 Pro Test (2GHz C2D Test Laptop – 2008)
Jan 2021 CU and MSFT drivers: nVIDIA GeForce, Conexant Audio/ Synaptics pointing pad using WUMgr 1.1b as the WU controller.
After some additional updates for MSFT/Windows Defender the system was up-to-date.
kb4535680 wasn’t offered so, nothing in the WUMgr sinbin.
SFC showed/s no violations post clean install via USB iso from MCT yesterday.

GP settings and previews disabled, non applicable services and scheduled tasks set to manual. Using only the provided tools within the OS to cleanup and optimise the storage SSD.

Today, ran a Defender Quick Scan that took over 4 minutes to complete, which was/is clean.
Then the following popup appeared:

MSFT, your timing is perfect /facepalm
anyone elses scan times perfect?

Attachments:

You must be logged in to access attached files.

Reply | Quote

[280park]

Re: KB4535680

Microsoft states that KB4535680 is offered only to certain specified versions of Windows. Susan Bradley also includes a list of those versions in her Computerworld article. The list does not include Windows 10 Pro version 2004 which is the version on my computer.

Has anyone been offered KB4535680 on a computer running Windows 10 version 2004? Can I be confident that it will not be offered to me?

Reply | Quote

[b]

It does not appear to be applicable to versions 2004/20H2:

This security update applies only to the following Windows versions:

Windows Server 2012 x64-bit

Windows Server 2012 R2 x64-bit

Windows 8.1 x64-bit

Windows Server 2016 x64-bit

Windows Server 2019 x64-bit

Windows 10, version 1607 x64-bit

Windows 10, version 1803 x64-bit

Windows 10, version 1809 x64-bit

Windows 10, version 1909 x64-bit

Security update for Secure Boot DBX: January 12, 2021 [KB4535680]

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4535680

1 user thanked author for this post.

280park

Reply | Quote

[ECWS]

Saw this today: KB4598291.  How long before the final version comes out?

Attachments:

You must be logged in to access attached files.

Reply | Quote

[DriftyDonN]

KB4598481,kB4586876,KB4598242 all installed manually on pro 2004  with no issues.

Now win10 pro version 2004 (OS Bld 19041.746)

Reply | Quote

[Coldheart9020]

ECWS wrote:

Saw this today: KB4598291. How long before the final version comes out?

The upcoming Patch Tuesday 2021-02 CU will supersede the Preview seen here. I have a similar one available for 1909 (KB4598298). These disappear once the final released patch makes the ‘Preview’ redundant.

Reply | Quote

[DriftyDonN]

I got this “offer “late today also. Do we have to install the feb tues patch to get rid of the “offer” ?

Thanks

Reply | Quote

[Coldheart9020]

When WU updates itself with the upcoming Patch Tuesday CU for February, the Preview will disappear on its own as it will by then be obsolete.

Reply | Quote

[Kathy Stevens]

Be warned. After installing KB4584229 and KB4598301, on a Windows 10 Pro, version 1909, build 18363.1316 workstation, I lost a large number of shortcut desktop icons.

Reply | Quote

[Susan Bradley]

Can you try rebooting?

Susan Bradley Patch Lady

Reply | Quote

[Kathy Stevens]

I have and the icons did not return.

I recovered my desktop icons from a backup.

Reply | Quote

[PDX5802]

WIN 10 Home, v2004.  Dell Inspiron 3880 w/ssd. AV disabled before updating.

Had a real problem with KB4598242.  Loaded 100% but failed to install. Ran WU troubleshooter, nothing. Ran CMD to stop wuauserv and bits, cleared software distribution download folder files, restarted wuauserv and bits. Did a system restart, KB4598242 downloaded 100%. Again failed to install.  Shutdown and restarted. This finally kicked it into installing. Checked update history and installed updates, it was there. Everything else on the OS seems to be working.  Have 20H2 waiting but in no hurry to install that before MS does it for me.  Back on pause until March 5.

Reply | Quote

[Alex5723]

PDX5802 wrote:

Have 20H2 waiting

20H2 is a minor update to 2004 (just like 1909 to 1903).
I have updated to 20H2 just 3 days after installing 2004.

Reply | Quote

[DriftyDonN]

Only thing I see on 20H2 that I am sure I don’t like is being force fed Edge and it being so ingrained that it cannot be blocked or removed.

Reply | Quote

[Lawrence Patterson]

Hello, just reporting in on a successful but strange applying January’s updates on a Dell PowerEdge R510 running Windows Server 2016 – 1607 Hyper-V host (with Exchange, File, DC Hyper-V guests) and being aware of Susan’s advice on KB4535680 (the video was very informative, thank you).

So the quick synposis, 3 reboots (last 2 done on its own), taking 45 minutes (normally ~20 min. and one reboot) timed from after triggering the restart.  The reboots and the time are not typical for this unit.  Though the Hyper-V guests started on their own with no issues.

Didn’t do anything different from previous months – wait till the end of the month updates, and when I launch the Install for KB4535680 (Sec. Updt.) – KB4598243 (Jan. CU) – KB890830 (Win. Malic. Sftw. Rem) and Defender update.

The Hyper-V guests were updated – rebooted successfully the week before, no issues or anything noteworthy to report.

Posted in case someone else has a similiar setup and looking for feedback.

Take care,

 

IT Manager Geek

Reply | Quote

[Chris B]

I just upgraded from 1909 to 20H2 on two machines and noticed two anomalies – the second more serious than the first.

The advanced settings in Windows Update, to defer updates, have now disappeared, rather than being greyed out. That does not bother me, since I use group policies editor, but it is a little strange. Maybe they have gone simply because I have the settings determined by group policies, and Microsoft thinks the greying option confusing.

The second, however, is more concerning. I found that the system restore function had been turned off completely. This had happened on both of my/my wife’s machines, but also on my son’s, which uses a different backup utility. They are back on now, and the setting has stuck, but this seems a trap for the unwary.

The systems are all Dells, and XPS and two Vostros, all running windows Pro.

Chris
Win 10 Pro x64 Group A

Reply | Quote

[PKCano]

The deferral pulldown switches in the GUI in Windows Update have been missing since 2004 was released. That is not new.

You may have not noticed it before, but System Restore has also been turned off when doing Feature Updates since multiple versions ago for me. I haven’t upgraded to 20H2, so I can’t speak for that upgrade, but it has happened with other upgrades in the past.

Reply | Quote

[John]

@PKCano, I updated from 1909 to 20H2 on Jan 11th, and System Restore was left switched on.

Dell Inspiron 7580 i7 16GB Win 10 pro

Reply | Quote

[PKCano]

Good to know.
This may be because it is the same core as 2004 with just the Feature pack turned on.

Oops, misread. See #2341321 below.

• This reply was modified 3 weeks, 1 day ago by PKCano.

Reply | Quote

[Chris B]

Interesting. My upgrade path was exactly the same as @barcud, just later – on 3 Feb and allowing the Jan updates to install.

Chris
Win 10 Pro x64 Group A

Reply | Quote

[Chris B]

@PKCano Indeed I have missed them both- sorry! But isn’t the switch off of System restore rather dangerous, in that it removes the user’s protection if something goes wrong? What do you think is the rationale?

Chris
Win 10 Pro x64 Group A

Reply | Quote

[PKCano]

In your case, you are moving to a different core when upgrading from 1909 to 20H2..
I see from above ( @barcud ) that System Restore is evidently staying on with same-core updates now.

Reply | Quote

[Chris B]

Perhaps I misunderstood. If we both moved on from 1909, didn’t we both have a core update?

Chris
Win 10 Pro x64 Group A

Reply | Quote

[PKCano]

No.
1903 and 1909 share the same core, have the same CU and SSU.The difference is in 1909 the Feature pack is turned on.

2004 and 20H2 share the same core, have the same CU and SSU. The difference is the Feature pack is turned on in 20H2.
But the core is different than 1903/1909.
2004/20H2 do not not share the same updates with 1903/1909.

Reply | Quote

[PKCano]

Ooops, I misread @barcud
You both did do  the same upgrade.
So my answer now is, I haven’t seen System Restore stay on in my upgrades.
I have always had to turn it back on afterward.
So I do not know what the difference is.

1 user thanked author for this post.

Chris B

Reply | Quote

[rggntljr]

Win 10 1909 [18363.1256 after updates applied] on Toshiba S55C laptop that was delivered with Win 10 1511: as usual, I allowed updates to “resume” with no internet connections available [blocks Windows update from running].  Immediately ran WU MiniTool for Windows selected updates and the Cumulative update was NOT checked: only 4 Office 2010 updates and MSRT. Allowed those to download/install with no problems.  Have also not been offered 2004 or 20H2 on this machine.  I do have the Conextant SmartAudio HD driver on this machine.  Is that the likely issue? rggntljr

 

Reply | Quote

[b]

rggntljr wrote:

Have also not been offered 2004 or 20H2 on this machine.  I do have the Conextant SmartAudio HD driver on this machine.  Is that the likely issue? rggntljr

Probably. See;

How to completely uninstall the Conexant audio driver from Windows 10 (and unlock the May 2020 Update)

Reply | Quote

[rggntljr]

Should have noted this is Win 10 1909 Home and the version # is unchanged from the time December updates were applied.  The last feature update that was able to be applied thru Windows Update was 1607 [AU].  All others have failed and had to be applied [in offline mode] from an ISO download, then updated after the feature update installed.  I expected the same going forward.  I understand the Conextant block may be impacting the 2004/20H2 display but I’m wondering why this month’s Cumulative Update was also unchecked in WUMT?  That’s a first.

Reply | Quote

[John]

PKCano wrote:

I see from above ( @barcud ) that System Restore is evidently staying on with same-core updates now.

@PKCano, surely a different core as I came directly from 1909?

Apologies, I didn;t see your later post!

Dell Inspiron 7580 i7 16GB Win 10 pro

• This reply was modified 3 weeks, 1 day ago by John.

Reply | Quote

[MrToad28]

I updated Win10 Pro from 1909 to 2004 using target release..The update history shows 2020-10 security update for V 2004 as latest installed..installed on 2/2/21..same as 2004. Only updates on offer are 2020-10 Edge..never used Edge. and 2021-Cumulative PREVIEW..not interested in beta testing that. Did the 2004 feature update include security updates through the 2/1/21 install date?

Reply | Quote

[Paul T]

Updating to 2004 will download the latest patched version from MS. If you download it late in the month is is likely to have the most recent patches applied.

cheers, Paul

1 user thanked author for this post.

MrToad28

Reply | Quote

[Bob99]

Did the 2004 feature update include security updates through the 2/1/21 install date?

To find out, right click on the Start menu icon and select the “Run” command. In the resulting white box that says “Open:” followed by a blank box with a narrow flashing cursor, type “winver” (without the quote marks, of course) into that box and hit Enter.

The resulting larger box that comes up should say you’re on Windows 10 “Version 2004 (OS Build 19041.746)”.

The part of the sentence in quotes is exactly what should show in the box if you’re fully updated to include the January updates.

I hope this helps.

• This reply was modified 3 weeks, 1 day ago by Bob99.
• This reply was modified 3 weeks, 1 day ago by Bob99. Reason: added clarity to sentences

1 user thanked author for this post.

MrToad28

Reply | Quote

[Alex5723]

DriftyDonN wrote:

Only thing I see on 20H2 that I am sure I don’t like is being force fed Edge and it being so ingrained that it cannot be blocked or removed.

You will be force feed ChrEdge on April.

Reply | Quote

[anonymous]

Hey guys-I could use some help. I saw on my windows updatte I can download and install 20h2. When I tried to tonight, nothing happened and it restarted the downloading process. I restarted machine after pausing it and I saw this in the detail of installed updates:

0x8024000b Failed to install

This code showed up. So I was wondering if there is a way to download the new update-should I tey with media creation tool or reboot the computer to install it that way, take out advanced systemcare?

I could really use your advice so I can install it safely and without harming my computer.

Reply | Quote

[anonymous]

Also can I use the WIndows Update/Upgrade assistant to install the 20h2 update?

Reply | Quote

[Susan Bradley]

Yes you can.  I’d recommend using that since the code sounds like the download got interrupted.

Susan Bradley Patch Lady

Reply | Quote

[anonymous]

Yeah I kinda accidentally paused the download when it kinda went back to getting things ready-before it was installing. Which can explain why the download interrupted-I mean it was out of curiousity ya know pause for 7 days and I was kinda doing stuff so I paused it by accident?

Also if by doing the Windows Update Assistant-it will download the version faster and safer I presume? 🙂 I can try it out tomorrow night. I mostly download new updates at midnight so there’s nothing going on.

Reply | Quote

[Susan Bradley]

Yes it will.

Susan Bradley Patch Lady

Reply | Quote

[anonymous]

Okay! ;3 Good to know! I think I’ll wait til the next level 4 to give it a whirl. Do it on my day off-usually I do my updates at midnight so there isn’t any interference or any disruptions. Sooo I’ll see when to do the updating to 20h2, gotta make sure to save my stuff on a USb drive.

 

Thanks so much :3

Reply | Quote

[castiel]

I got my Win10 Pro from 1909 to 2004 OK and things seemed to be good. But when I installed January’s KB4598242 Cumulative Update, things went downhill pretty quick. By that, I mean things got really slow not only after starting Windows, but even the Boot process as well. I finally restored using a system image I had made prior to KB4598242 and things went back to being OK again. Decided to repeat the install of KB4598242 and ended up in the same (slow) spot. Did some looking around and seems disk chugging at 100% a lot. Finally restored back yet again and used wushowhide to hide KB4598242. The thought of a driver problem crosses my mind, but which one(s) – if any. So, I got some work to do. Any thoughts out there of the most efficient way for me to get a handle on my KB4598242 problem? I see there are a zillion (do I exaggerate?)  things to “try”, but that could keep me busy “forever”. Any guidance would be appreciated.

Reply | Quote

[Susan Bradley]

I personally have not seen slowness.  Look for third party stuff – antivirus up to date? Any other start up programs that need to reindex?

Susan Bradley Patch Lady

Reply | Quote

[castiel]

I definitely have antivirus up to date. I had noticed “Scheduled Optimization” had been flipped from Off to On when I went from 1909 to 2004, so I have set that back to Off. Not seeing anything that is obviously indexing. I stayed with KB4598242 for a few days thinking the slowness would “clear up” but never did. What unnerves me is the Boot or Startup slowness that persists across multiple days. I am sorely tempted to take another system image and then unblock the driver updates offered up by Windows Update and let them install. If that fixes the problem then great. If not I restore back to my system image taken before. The problem is not with 2004 at the 19041.685 level, it appears when I install the KB4598242 January Cumulative Update. That’s the part that has me puzzled.

Reply | Quote

[Paul T]

castiel wrote:

disk chugging at 100%

That can be a lack of RAM causing Windows to page to disk. You need a minimum of 8GB for W10.

cheers, Paul

Reply | Quote

[castiel]

The device has 12GB of RAM. Again, I had no problem until install of KB4598242 which is puzzling to me. Remove KB4598242 (via restore of system image) and things go back to normal.

For now, I reinstalled KB4598242 and am living with a slow computer and looking for a clue.

Reply | Quote

[Paul T]

My reading of the fixes in that patch suggests you can safely remove it, unless your machine is an intranet server. I’d take it out and see if there is an update this month.

cheers, Paul

Reply | Quote

[castiel]

Since searching on the 2004 January Cumulative Update KB4598242 for slow startup problems was not helpful, I widened my criteria to “windows 10 2004 slow startup” to maybe find more clues. Yikes – that yields a great many posts (mostly rehashing the usual suspects – and none seem to have a solution).

Although I did say I got from 1909 to 2004 OK, it is true that startup under 2004 was slower than it was on 1909. Maybe I have been focusing too much on the January Cumulative Update.

There are a great many things to try, but it is consuming enormous amounts of time to go down each dead end. I have disabled and/or uninstalled many things. This gets performance OK after the system settles down, but does nothing for the slow startup time.

If I had unlimited free time, I would be tempted to do a clean install of Windows 10 to the 19041.746 build of 2004.

Reply | Quote

[Coldheart9020]

Are you using a HDD or SDD? If using a conventional hard drive, slow start up and other performance is not surprising, even with an otherwise decent system spec which more than meets system requirements.

Reply | Quote

[castiel]

The problem device is a laptop with a conventional hard drive. I did see from reading the posts on 2004 being slow at startup that many people mentioned a SSD as helping. The laptop hard drive is 1TB so SSD is not a good alternative for me personally (better to buy a new laptop).

I also have a desktop which is several years older and I upgraded it from Win7 to Win10 as a clean install of Win10 and reinstall of apps and data. So this desktop has also been upgraded from Win 10 1909 to 2004 and the same January update installed (KB4598242) but I am not seeing the same degree of slowness as on the laptop (by an order of magnitude).

I still have a very old device that still has Windows 7. When I power that on, Windows 7 starts up lightning fast in comparison to either Win 10 device. Sigh.

Reply | Quote

[Susan Bradley]

In this day and age SSD is mandatory with Windows 10.

Susan Bradley Patch Lady

Reply | Quote

[Paul T]

I put an SSD in an old W7 laptop and it was so much better. Updated to W10 and the start time was around 10 seconds.

cheers, Paul

Reply | Quote

[Author]

Posts