The “disappearing desktop” temporary profile bug is still in the February cumulative update for Win10 version 1903 and 1909. Looks like the bug’s in t
[See the full post at: MS-DEFCON 3: Get the February patches installed]
|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
-
MS-DEFCON 3: Get the February patches installed
- This topic has 166 replies, 58 voices, and was last updated 5 years ago.
AuthorViewing 72 reply threadsAuthor-
-
3) The profile bug may not be that widespread (unsure).
… and yet only four days ago Woody claimed that it was widespread.
We don’t have official acknowledgment of the widespread “missing profile” bug in this month’s Win10 version 1903 and 1909 cumulative updates.
-
Define “widespread”
1 user thanked author for this post.
-
-
… by the way, which “widespread attacks” make MS-DEFCON 3 appropriate today?
1 user thanked author for this post.
-
Define “widespread”
I have to agree with @b here. If you’re going to use the term, we readers need something a little less ambiguous than “widespread”, or at the very least more than anecdotal evidence to back it up.
I, for one, never took it to be “widespread”. I install every update Microsoft has to offer my five systems with nary an ill effect. For those who simply don’t pay attention to updates and let Microsoft update their systems automatically, that would leave them fully updated, like me, and unlikely to have problems, like me and the others who have reported similar results right here on AskWoody.
My son, for example, has two Windows 10 Home laptops, doesn’t give two hoots about updating, just lets Microsoft take care of that. He hasn’t had a single problem in the four+ years he’s been using these laptops.
As I’ve said elsewhere, 1% of Windows 10 installed base is ~10,000,000 installations. For me, “widespread” implies greater than 1%. To use another context, if users were polled, 1% would be much less than the margin for error of the poll.
And certainly my personal evidence is anecdotal, but it is firsthand, not secondhand or third-hand evidence. I’ve been waiting for the sky to fall since Windows 7 was introduced. I’m still waiting.
Always create a fresh drive image before making system changes/Windows updates; you may need to start over!We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.We were all once "Average Users".2 users thanked author for this post.
-
Widespread is a descriptive adjective, not a quantitative one. Think damp rather than percent saturated.
I believe a California wildfire is widespread long before it consumes 51% of the acreage, or relocates even 10% of the population. You folks are being absurd to assign such values to Woody’s chosen flourish. Just how many angels jitterbug on your pinheads?
I read Widespread to be beyond the scattered, isolated cases that are explained or at least suspected of being unrelated. Widespread is a word to suggest there is a commonality in cause. But language can be a funny thing. Not everyone approaches communication in the same manner.
-
Woody
Perhaps ‘widely reported’ would be a better term, one less level of abstraction.
Just because you don't know where you are going doesn't mean any road will get you there.
-
-
Both you and Woody are both correct. There have been a substantial number of reports by people bitten by this bug and likely many more that went unreported in forums.
What I was referring to was the percentage as it pertains to total Windows installs. Since Microsoft isn’t releasing any pertinent data, we simply don’t know. Is it 10% or less than 1%?
In all honesty, this this first time I’ve waited this long into the update cycle to apply patches (I don’t have my sacrificial Win 10 computers running yet).
4 users thanked author for this post.
-
-
-
-
What’s the status of Office 2010? I have two updates in my Win 7 WU; are they safe?
Note: The Master Patch List does list these, but does not approve them for installing.
Being 20 something in the 70's was far more fun than being 70 something in the insane 20's1 user thanked author for this post.
-
-
-
Just after the discussion of this slide, the “host” asked about the difference between “feature updates” & “quality updates”. Woody’s interpretation in the past was that “feature” referred to new versions (Ex. going from 1903 to 1909 to 2004 to etc.). “Quality” referred to the usual monthly patches. Also…
even though I’m still on Windows 8.1, I’m thinking to allow “telemetry” to do its thing. M$ could be spying, it could not be… but if telemetry is tracking issues, I’d prefer to let it. I know it’s not the only tool they have regarding Win10 or December’s Win10X… but it might be the only tool for Win8.1 now. Since there’s less than 3 years left for it… BTW, does that mean I’ll start applying updates ASAP on Patch Tuesday? As I would tell the “expert” on the left in the video… Do I Look Stupid?! Following MS-DEFCON until I finally convert to Linux or migrate to Win10!
EDIT: If I migrate to Win10, I’ll continue following MS-DEFCON. Why wouldn’t I?
Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again... -
-
Telemetry is just collecting information. It does not change your settings.
--Joe
1 user thanked author for this post.
-
The EULA is where the real intent can be found and everything that the 10 EULA spells out is very worrisome indeed. And Grabbing files along with the error data is a slippery slope to a privacy violation. Plus with all of someones data stored in MS’s cloud wire-shark is sure not going to show any repetitive brute force activity for data that may be hosted in any cloud based systems and TLAs simply vacuuming up that information, encrypted or not, for some later cracking.
Telemetry is a rather broad term as that’s inclusive of any and all according to the EULA and that’s where the rational mistrust comes in from folks that value their privacy.
1 user thanked author for this post.
-
-
-
It feels like there is a widespread belief that, even when security does not seem to be relevant, even if a patch seems to be not that great, because of possible future failure of updates to install, you should rarely skip a month or three of patches. Are there statistics that show that cumulative windows 10 updates are more likely to fail when you have skipped a month? My experience is when I skipped a few months the next one installed fine.
1 user thanked author for this post.
-
I don’t know of any definitive answer. Subjectively, it’s very unusual for a cumulative update to go bonkers if the preceding cumulative update isn’t installed. Don’t think I’ve ever seem that.
The real crapshoot every month is whether a vulnerability will get exploited before you install the next patch.
-
-
-
Installed the ‘puny’ kb4537821 and MSFT adobe flash patch without any issues earlier this month on one x64 win 8.1 Pro device and the other two devices were updated a week later.
Windows - commercial by definition and now function...1 user thanked author for this post.
-
My 90 day deferral of Feature Updates expired for Window 1909 a couple of weeks ago and I allowed the in-place upgrade from 1903 to happen on 2/12/20. No ill effects noted so far. I can’t speak to the File Explorer search issue because I haven’t used File Explorer search.
What’s interesting is I appear to have gotten the February CU when I did the Feature Update. I have a 15 day deferral for Quality Updates which expired this past Wednesday. But, the only updates I have been offered were for Flash and the MSRT, both of which I installed without issue.
I have not had any problems with my user profile.
-
I’ve had WU paused since I was one of the unlucky to get the temp profile bug (win 10 pro x64 1909), with KB4532693 only on one machine, uninstalled the patch and back to normal, other machine installed KB4532693 without issue.
The last week I’ve been doing some of my own trouble shooting to try and get KB4532693 to install on the problem machine, one user (local admin account) from disabling start up entries, removing third party anti-virus software, rebooting into safe mode (which I might add had an working profile, but restarting was back to the temp profile) nothing worked.
I had KB4532693 stand alone package downloaded from Microsoft Update Catalog.
I was finally able to get KB4532693 install without the temp profile bug by adding another user local admin account, logging into that account and installing the stand alone package, windows update was still paused.
I’m no longer faced with the temp profile bug, and removed the new local admin account.
-
OK so I am with Woody on moving from 1903 to 1909.
Currently I have 1903 Pro x64 updated thru January. Group Policy setting = 2 (ask before download), Feature update set at 365 deferred days, Quality updates set to 0, with wushowhide currently hiding all February 1903 updates.
Normally I would dial back the Feature update deferral to a more recent number and wait for Windows updater to update and present the more recent Feature (1909) for download. Then click Download to install.
Should I do it that way, or as you suggest simply press the Check for Updates button and see if 1909 appears along with the Download and install link? Then press that link?
Normally after a Feature Upgrade Download, I would disconnect from the internet before rebooting, reboot, then check out all settings and changes before rebooting again and going back on line.
Since the Feature upgrade from 1903 to 1909 was/is reportedly a “special flip the switch” type upgrade – should this changeover be handled any differently?
Finally, I assume if I move from 1903 to 1909 that there is no need to install ANY of the 1903 February updates as they are the same as for 1909 and should install with the 1909 Feature upgrade – correct?
Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)1 user thanked author for this post.
-
I would do it the way described in the article. That’s how I did it, anyway, and it worked.
“Flip the switch” is just marketing jargon. You should make a backup, but I don’t think any other special effort is necessary.
And, yes, you end up with 1909 with the Feb updates installed. But NOT the optional updates.
1 user thanked author for this post.
-
-
You should make a backup, but I don’t think any other special effort is necessary.
That is my standard practice, only substitute “drive image” for backup, and any other special effort (like the MS-DEFCON rating) is not necessary for home users of Windows 10.
For IT professionals riding herd on lots of PC’s in a business environment, I completely understand the need to test updates/upgrades on a PC setup up for that purpose, and be satisfied that the update/upgrade will not disrupt the business before full-scale deployment.
But in my view that is simply overkill for home users. A good drive image will negate, in a matter of minutes, any negative consequences an update/upgrade might potentially have. You, The Patch Lady, @PKCano, @Kirsty, @microfix, and many others emphasize having backup before an update/upgrade. I emphasize “drive image” rather than the somewhat ambiguous “backup”, but all the rest of the hand-wringing seems superfluous and unnecessary.
Always create a fresh drive image before making system changes/Windows updates; you may need to start over!We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.We were all once "Average Users".1 user thanked author for this post.
-
A good drive image will negate, in a matter of minutes, any negative consequences an update/upgrade might potentially have.
Assuming you notice the negative consequences pretty quickly.
1 user thanked author for this post.
-
-
-
How about the:
Normally after a Feature Upgrade Download, I would disconnect from the internet before rebooting, reboot, then check out all settings and changes before rebooting again and going back on line.
Or are the normal concerns associated with a Feature Upgrade not applicable with 1903 t0 1909?
Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP) -
I haven’t seen any reason to go to superhuman lengths to update from 1903 to 1909 offline.
1 user thanked author for this post.
-
I always check my settings to see if they are where I left them and if any new features (that I don’t want) are turned on by default before I go back online. But that’s just me.
1 user thanked author for this post.
-
-
-
-
-
-
-
There was an SSU KB4537829, but only if you purchased and ESU subscription.
1 user thanked author for this post.
-
-
-
I decided that it was time to take the update plunge. Totally updated both mine and my wife’s Dell laptops ver 1909 and running Windows Defender AV. Everything went as advertised with no problems. Now I can’t wait till next Tue when we can do it all again.
1 user thanked author for this post.
-
-
Thanks but no thanks. When the Feb. bugs are corrected in Mar. and the Mar. bugs seem to be under control I’ll reevaluate and maybe update then. For now, nothing in the Feb. updates to v1903 make me weak in the knees with anticipation. I’m too lazy to deal with a disappearing desktop even if the chances of that happen are not very good.
It is Microsoft’s fault that I choose to play it safe rather than be sorry.
1 user thanked author for this post.
-
-
Patch reliability is unclear, Go ahead and patch, but watch out for potential problems.
not very comforting…..woody, you always say if you dont NEED a patch why patch? paraphrased- why do we NEED this feb patch? I havent seen anyone say anything good about it….
D
1 user thanked author for this post.
-
It’s a juggling act.
By patching now, you’re hedging your bets on whether a vulnerability will appear before you decide to install next month’s patches. I don’t see any imminent threats (except for admins with servers), but the bugs seem to be well-understood.
3 users thanked author for this post.
-
-
Changed deferral settings, disabled Kaspersky A/V and ran check for update (1809).
Got .net , flash and 1909. No KB4532693 yet. User still “alive”.
1 user thanked author for this post.
-
-
-
-
The requirements are listed for KB4539601 2002-01 Preview of Monthly Rolllup. It has appeared in the Optional queue on my Win7 machines. It contains the “fix” for the stretched screen. I have not tried to install it, or the required SSU that is standalone and not offered through WU.
There is also a smaller standalone “fix” KB4539602 (requirements).Check here for other options.
1 user thanked author for this post.
-
-
-
You mean this?
I haven’t heard of any complaints after MS changed the files on Feb. 10. If you have, I’d sure like to hear about it!
that’s why i was asking in my first post here: is it safe to install?
and abbodi86 answered: “It’s not”PC: Windows 7 Ultimate, 64bit, Group B
Notebook: Windows 8.1, 64bit, Group B -
-
-
-
-
-
All done, no issues, on Win. 10 Pro (desktop) and Win. 10 Home (laptop), just in time to keep the firm’s I.T. guy happy when he comes on Monday.
1 user thanked author for this post.
-
Win10 1909 Pro Dell desktop with PKCano’s recommended registry settings. Feb patches installed this morning, no apparent issues.
wushowhide still showing KB4497165 available (Intel microcode update), but it didn’t come down the MS update chute.
Win10 22H2 Pro, MBAM Premium, Firefox, OpenOffice, Sumatra PDF. -
wushowhide still showing KB4497165 available (Intel microcode update), but it didn’t come down the MS update chute.
Same for me: Win10 1909 Pro Dell device with PKCano’s recommended registry settings. A slight difference with regard to the Feb 11 patches: all three were hidden Feb 11, but MSRT and .NET unhidden later and downloaded/installed. So, Feb CU KB4532693 remains hidden. Then I hid KB4497165 (microcode update) on Feb 25 when it was released, but unhid it on Feb 27 (two days ago), but it hasn’t come down the chute yet, similar to what @TonyS describes. But, Defender definitions (never hidden) and the Defender platform update (never hidden) came down the chute on Feb 28 and downloaded/installed with the Download button, hence jumping over the unhidden KB4497165. So, KB4497165 must be digging in its heels, though unhidden; it seems to be stuck there.
I wonder how one can “jiggle it loose”??
1 user thanked author for this post.
-
-
-
-
Win10 1809 Home here. Just reporting that I have installed the following February patches without trouble:
– KB4532691 2020-02 Cumulative update
– KB4537759 2020-02 Security update for Adobe Flash Player
– KB4538156 2020-02 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8
– KB890830 Windows Malicious Software Removal Tool x64 – February 2020I also installed (without any apparent issue) the following Office 2013 patches released this month:
– KB4484265 – Security update for Microsoft Excel 2013
– KB4484156 – Security update for Microsoft Outlook 2013At this time, I skipped installation of KB4494174 (Intel microcode update), but I might install this one later on. Also, I have not installed the infamous KB4023057 (and do not plan to install this one at all).
BTW, for the time being I’m staying on 1809, but will consider moving to 1909 later this year when 1809 reaches EOL. Hopefully, by that time the “disappearing desktop” temporary profile bug will get sorted out.
-
-
I installed the Feb 2020 updates on my Win10 1909 PC two days ago, and everything seemed fine until the first time I came back after the screen lock had initiated. Before the updates, any input (keyboard, mouse) would bring up the password screen. After, it required Ctrl-Alt-Delete. That in itself is not a problem, but after the PC was unlocked, it would repeatedly re-lock by itself every 20-30 seconds. I changed to timeout from 30 to 40 minutes and that took care of the spontaneous re-locking. But when the machine locked again after 40 minutes (or initiated manually), the same repeated login problem was back.
I rolled back to the image I’d done immediately before installing the updates, and the problem was gone. I didn’t see anything involving that issue in the KB4535996 list of fixed issues, but I’m tempted to try the Feb 2020 updates again, followed by KB4535996 and see if it has any effect.
-
Did you install the Feb Cumulative Update before the problem appeared – or did you install the “optional” CU, KB 4535996?
There’s a reason why those patches are optional – and why I warn against installing them…
1 user thanked author for this post.
-
Woody, thanks for your reply, and no, I didn’t and have not installed KB 4535996. Only the Feb Cumulative Update. Believe me, I also stay away from any optional updates.
I may unpause WU and do a screenshot of what it’s wanting to download. That way I can document exactly which updates are coming down the pike.
Dang, I was looking for the “reply” button for this comment and didn’t see it until after I posted.
-
After three tries, the Feb updates finally worked, and so far none of the weirdness reported in my original post has occurred. Fingers crossed!
1 user thanked author for this post.
-
-
-
Changed deferral settings, disabled Kaspersky A/V and ran check for update (1809).
Got .net , flash and 1909. No KB4532693 yet. User still “alive”.
Corrections to my previous post.
Updated to 1909 from 1903 (not 1809).
Got KB4532693, KB4537759, KB4517245 and KB4538674. All found under ‘Uninstall an Update’.
-
-
I was under the impression that that KB was now part of current 1909 Feature upgrade.
It was included with the 1909 update but doesn’t appear under the list of updates, only under the ‘uninstall’ list.
The whole process of download-install-re-boot 3 times.. took less than 10 minutes. I am on 1Gb optic fiber, i7 6 cores CPU and 16GB of RAM.1 user thanked author for this post.
-
-
-
-
I received today:
KB4537572 2020-02 Cumulative Update for .NET Framework 3.5 and 4.8 for Win10 1909 for x 64 NO PROBLEMS INSTALLED
KB 4497165 Update for Win 10 1909 x 64 was there, then disappeared and did not reappear?
Can you hide the optional updates or just let them sit there?
Win 10 Home 22H2
1 user thanked author for this post.
-
I upgraded my main desktop today from Windows 7 x64 to Windows 10 1909 x64 (Home). No issues as yet.
1 user thanked author for this post.
-
Here are my updating results:
I have been on version 1903 on the refurbished laptop I got in November to dual-boot with Linux Mint. Today, after a fresh image backup, I changed the deferral setting, turned off metered connections, and successfully installed the following:
— Win10 1909 feature upgrade, getting the February CU KB 4532693 in the process, as Woody explained;
— KB4537572 .NET;
— KB4537759 Adobe Flash; and
— KB890830 Malicious Software Removal Tool.
— KB4052623 Windows Defender antimalware platform also installed, though it seemed to install separately and before the others, maybe at the same time as the latest definition update.All seems to be well, and I’m encouraged that at least this first (small) feature update went well. The laptop did reboot a second time for some reason, but there weren’t any problems.
I’ve hidden the microcode update, KB4497165, at least until I do more research to see if it’s needed.
For Windows 7, I installed the 2 Office 2010 security updates together with the MSRT. Windows Update seemed stuck a long time on the Excel update (KB4484267), although I wonder if the MSRT was actually the culprit, since it often takes a long time when I install it separately. Eventually all 3 installed successfully, anyway.
Thanks as always to Woody, PK, Susan, and everyone else who posts here for your help with another month of updating.
Linux Mint Cinnamon 21.1
Group A:
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux
Win l0 Pro x64 v22H2 Haswell, dual boot with Linux
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux,offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline1 user thanked author for this post.
-
There aren’t many Win 8.1 users out there, but for those who are using it, here’s a data point.
On a Win 8.1 pro 64 bit machine I installed the February Rollup, Flash, and .NET updates (KB4537821, KB4537759, and KB4538124, respectively) last night. Rebooted after the .Net and Rollup patches.
A very quick uneventful patch job.
-
-
Just installed everything except KB4535996.
So far nothing “interesting” to report.
18363.6571 user thanked author for this post.
-
-
Belay that question – i figured it out.
In Advance Settings, I had manually set to delay quality updates by 30 days. Hitting “Resume Updates” on the landing page apparently does not overcome that manual setting.
So I just now set it to zero, and I am getting a bunch of 2020-02 updates.
Sorry. And thanks again to Bill Gates for keeping it so simple and easy.
1 user thanked author for this post.
-
-
1 of 3 MS Update / Security patches wipes out Windows Desktop. They updated 2/29/2020 with the shutdown and installed 3/1/2020 when the system was booted up in the morning.
KB4532693, KB4537759, and KB4534132.
Windows boots to a temporary desktop. Suggests to logout and log back in to fix. Doesn’t work. Logs into same temp desktop.
Tried Windows Backup Restore to previous date but this didn’t work. Had to uses Windows Update & Security, View Update History, Uninstall Updates. Locate 3 files under Microsoft Windows section (bottom of updates list).
1 user thanked author for this post.
-
-
what exactly is this culprit responsible for? It installed on my machine yesterday with no obvious bad results? see edit below….
win10 pro ver1909 bld 18363.657
Thanks!
kb4534132 installed 10feb no obvious issues, the other two (I dont have the kb#’s handy) also installed w/o issue 29Feb. Also upgraded 1903 to 1909( kbxxxxx132 installed into v1903) not certain if the other 2 installed just prior to upgr to 1909 0r with the upgrade
so all three of the mentioned kb’s installed ok…so unless these are pc specific errors due to these kb’s we are still in the dark I guess….
D
-
-
-
-
Update on 1903 to 1909 upgrade on my Win 10 Pro laptop:
All seems fine after the upgrade.
Took about 30 minutes – restarted twice, and did seem to be slow downloading, but that is probably my connection. Now on build 18363.657 – and no other updates pending.
Checked my settings – nothing seems changed – even Cortana and search settings off remained the same.
Keeping fingers crossed that things are smooth from here on in, but way less stressful that I was anticipating!
1 user thanked author for this post.
-
Windows 10 1903 to 1909 upgrade is supposed to fairly quick and painless, as the two share the same core components and files, according to Microsoft.
Windows 10, versions 1903 and 1909 share a common core operating system with an identical set of system files. As a result, the new features in Windows 10, version 1909 were included in the latest monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant/disabled state. These new features will remain dormant until they are turned on via an “enablement package,” a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.
Windows 10 Pro 22H2
1 user thanked author for this post.
-
-
I just updated my HP ProBook G2 laptop from 1903 to 1909 18363.657. I ran chkdsk 1st, then DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow and cloned my laptop.
I went to Grp Pol and disabled the 365 day hold on Feature Updates and then went to settings>WU>advanced and removed the 30 day pause, then checked for updates. It gave me KB 4537572 (.net), MSRT, KB 4537759 (Flash), & KB 4532693 (cum. updt 4 1903 and rebooted to 1903 18362.657.
So I checked for updates again and there was 1909, so I installed that and it went smoothly to 1909 18363.657.
Then I [messed] up
I clicked on pause for 7 days and thought it’s way too early for that and clicked on Resume updates and it found that dang Optional .net, so I just left it there and shut down the laptop.Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).1 user thanked author for this post.
-
I got 3 computers done today from 1903 to 1909 without a hiccup (same procedure as the laptop above). All seem to be ok. Got one more to do but it will have to wait until tomorrow.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop). -
Last computer done. No User Profile issues on any of the 4 computers. Whew!!!!
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
-
-
-
-
-
I converted my laptop from Win 7 to Win 10 1909 build 18363.418 installed Jan 17, 2020
In January, I took Woody’s advice to pause updates, and then I read PKCano’s suggestion to use Group Policy Editor and enable “Notify for download and auto install.” Today is March 1, 2020 and I see this notification
Is there supposed to be a way to select these updates individually?
Or am I limited to just clicking the download button and getting them all?
For example, I don’t need or want Flash Player.
Thank you.
-
If you run “wushowhide” you can select and hide the patches that you don’t want. Then re-run “check for updates”.
Windows 10 Pro 22H2
1 user thanked author for this post.
-
FlashPlayer is built in to IE and Edge in Win10, not a separate install like it was in Win7.
You need the Security Updates.You can use wushowhide.diagcab to hide updates. Download it from Microsoft.
2 users thanked author for this post.
-
Update to post #2174552
After seeing the replies above I went ahead and clicked “Download”. It took some time because I have an extremely slow speed ISP, but a couple of reboots later there were no error messages, and the desktop looks normal. Thanks again for all the advice here.
1 user thanked author for this post.
-
-
This may be old news by now. I just successfully tried the newest simple way to extend the pause updates date as mentioned on your forum.
I am a cautious soul, so am staying with Win 1903 build 18362.535 from November 1st 2019.
I have been able to keep extending the update resume date by first ensuring that I am not connected to the internet, (Wireless off) and disable any Ethernet in network connections. No need to unplug cables etc.
I then click resume updates, it fails (thankfully) and this gives me the ability to click ‘pause updates for 7 days’ multiple times to get a new resume date. That date is currently 4/4/2020. I last did this yesterday (February 29th).
I have been doing this every few weeks for the last few months, so have an infinite extension going.
Not going to update until you report that the ‘disappearing desktop’ issue is resolved – hopefully before a new set of buggy updates arrive.
Edited for HTML
5 users thanked author for this post.
-
-
-
Have you set “Pause” on updates? If so, they won’t show up.
You also have to be sure Metered connections are turned off.1 user thanked author for this post.
-
-
-
-
In your case, I would wait until after the March updates to upgrade to 1909 to see if MS has fixed the issue (which they haven’t admitted exists).
1 user thanked author for this post.
-
-
The ‘Irene’/’PKCano’ exchange is immensely helpful. Thank you, both, and well put!
1 user thanked author for this post.
-
If the install of the Feb patches on 1903 go without any problems, maybe it would be good to go ahead and install the upgrade to 1909. The patches are basically the same except the new features are turned on in 1909. It should be a rather painless experience.
Go ahead and do the upgrade to 1909 if Feb patches don’t cause any problem.
1 user thanked author for this post.
-
-
KB4997165 is Intel microcode. I have not been installing the microcode patches, hiding them instead.
The two Win10 Pro that upgraded to 1909 were both Intel. I had no problems (that is no guarantee, of course). I did it by lowering the Feature deferral to 80 days, then putting it back to 365 before reboot.
The .Net patch should be OK also.
1 user thanked author for this post.
-
-
-
-
-
-
-
-
-
Where is “resume update” I don’t have this button ?
It only shows up if you click “Pause for 7 Days”
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
-
-
-
I want to say thank you to Thankfully Retired DBA for that post. Your method for extending the time to pause updates looks to be the easiest I have read so far.
My other two desktops (8.1 and 7) are connected to the internet via cable as they are beside the router but this new Win 10 is strictly wireless as it’s in another room. Per your method all I have to do is make sure I turn off the wireless (airplane mode?)
1 user thanked author for this post.
-
febPatches and v1909 feature up occurred as follow:
Note xxxx.net install twice(diff dates) how come that? Also why is update history different from uninstall options?? -
About your questions — this is what I can tell you
You can check the MS-catalog for supersedence chains. It turns out that 2/10/2020’s .NET KB4534132 replaced 1/25/2020’s .NET KB4532938 Looks like a correction was needed. See a sample from the MS-Catalog that shows the supersedence chain for your .NET KBs.
“Uninstall updates” will list SSUs, which are ‘wrappers’ from some CUs. For example, SSU KB4538674 is a wrapper for CU KB4532693. SSUs/wrappers are not listed in Update History. {SSU=Service Stack Update.}
The MS support page for KB4532693 will tell you what SSU is needed.
Below is a clip from the MS-support page for KB4532693 that contains info about the required SSU.
1 user thanked author for this post.
-
-
-
One thing i noticed is that nobody in this thread has indicated that they were hit by the disappearing desk top bug.
Just thought i would throw that out.
Barry
Windows 11 v23H22 users thanked author for this post.
-
Linux Mint Cinnamon 21.1
Group A:
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux
Win l0 Pro x64 v22H2 Haswell, dual boot with Linux
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux,offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline
-
-
-
Check for updates is no longer the “I want everything” button on 1903 and up.
https://www.askwoody.com/2019/things-i-didnt-know-check-for-updates-in-win10-1903-now-warns-about-optional-and-feature-updates/cheers, Paul
-
-
-
-
-
-
-
-
-
Well, that’s interesting. The information below the processor list says “This update is a standalone update that is targeted at Windows 10, version 1903 and Windows Server 2019, version 1903.”
It was in both of my Win10 1909 WU queues on Feb 25, at which time I hid it. I unhid it on Feb 27 but it has never reappeared in the queue. {Wushowhide indicates that it is unhidden.} So, does that mean that Microsoft realized it was a mistake to send it to my 1909 queues on Feb 25 and won’t let it show up in the queue, even though it’s been unhidden??
There is also no superscript 2 (for note 2, which says “As of February 25, 2020, the update for these select products (CPUs) are available through Windows Update” for my 1909 processor i7-6500U Skylake U and my other 1909 processor i7-8565 Whiskey Lake U — which means if there is no note 2, the update is not available through WU. Nevertheless, KB4497165 DID appear in both 1909 queues on Feb 25 !?!
1 user thanked author for this post.
-
-
-
KB 4497165 is a mystery. I have Win 10 1909 HOME and when I check WUSHOWHIDE it is there to hide, however, not in the Windows Update area.
It does not show up to download, yet WUSHOWHIDE says it is there to HIDE.
I therefore, hid, then unhid the update and then it told me there was nothing to UNHIDE.
It’s playing a game with me.
Perhaps it is hidden by the OS itself since it is 1909?
The Microsoft Product note states:
This update is a standalone update that is targeted at Windows 10, version 1903 and Windows Server 2019, version 1903. This update also includes Intel microcode updates that were already released for these operating systems at the time of release to manufacturing (RTM). We will offer additional microcode updates from Intel through this article for these operating systems as they become available to Microsoft. Use the registry settings as described in the Windows client and Windows Server KB articles. (By default, these registry settings are enabled for Windows client OS editions and Windows Server OS editions.)</p>
Consult with your device manufacturer and Intel through their websites regarding their microcode recommendation for your device before you apply this update to your device.Win 10 Home 22H2
1 user thanked author for this post.
-
-
It’s microcode updates for Intel processors. It may be that it’s not applicable to your processor.
But, both of my processors are on the list, which, to me, means that it’s applicable to my processors. And they appeared in my version 1909 WU queue {which I hid and then later unhid}.
However, the MS-URL for this microcode update KB4497165 says it’s for 1903 (i.e., not for 1909).
So, in short, there’s a disconnect between what the MS-URL document says (no, not for 1909) and what is being released to the WU queue (yes, for 1909). (It’s quite possible that MS has now realized the disconnect and consequently has it “quarantined” so although unhiding it puts it in the queue {at least as far as wushowhide functions}, the queue is not going to let it out.)
More about the disconnect:
It’s in the MS-Catalog and 1909 is listed there. The main list says that it was
last updated on 1/29/2020, but the update details say it was last modified 2/25/2020. {I swear that I saw it in the main list on Feb 25 with a last update of 2/25/2020, but now it says 1/29/2020 there.}
1 user thanked author for this post.
-
However, the MS-URL for this microcode update KB4497165 says it’s for 1903 (i.e., not for 1909).
It says 1909 at the top (but not at the bottom; I sent feedback to that effect).
2 users thanked author for this post.
-
The MS-URL page and the MS-Catalog listing have changed since I first sent my note. I did not make a snapshot of the MS-URL page, but I did make one of the MS-catalog listing. Below is the MS-Catalog page that I saw at 4:13pm and the one I saw at 6:49pm. They are different. Maybe the 6:49pm change is due to your report.
But, anyway, this still doesn’t solve the problem of KB4497165’s being in the queue on Feb 25, hidden thereafter, then unhidden on Feb 27, and its yet not reappearing in the WU queue, despite the fact that my version is 1909 and my processors are on the processor list.
-
-
-
-
My wife’s PC is a 3-month old Dell Inspiron-15 model 5594. We set her Windows Update as PKCano suggested with the Group Policy editor. It is on Win 10 ver 1909 (build 18363.535)
Today she is offered the following by WU, and I am surprised to see the Intel items.
The Dell Update program version 3.1 on this machine reports this system is up to date.
Are these Intel patches safe to install?
I have never used wushowhide but perhaps I should learn more about it if I want to accept/reject these patches individually.
Thank you very much.
-
-
But you should also read AKB2000013 about clearing the update queue after they are hidden, because if they are still showing in the Update queue after hiding they will download/install when you click “Download.”
OR, if you are not in a hurry, use wushowhide to hide the updates that you don’t want to install then do nothing – wait for Windows to run its next automatic update (18 – 24 hours) after which the updates you previously hid in wushowhide will no longer show on the Windows Updater screen. You can then safely install the ones that are showing by pressing the Download button (Windows 10 PRO with Group Policy setting 2 for ask to Download/Install). Key is you will Download what is shown on the Settings>Windows Update screen regardless of what you just did with wushowhide. Wait for the update or use PK’s process referenced to clear the queue.
Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)2 users thanked author for this post.
-
-
-
-
I am surprised to see the Intel items
As usual with Microsoft these are old Intel GPU/Audio drivers.
The latest Intel driver is Intel DCH 26.20.100.7870
https://downloadcenter.intel.com/download/29426/Intel-Graphics-Windows-10-DCH-Drivers?product=80939I have installed this driver on my Windows 10 Pro 1909 with i7-8750H UHD630 GPU.
1 user thanked author for this post.
-
-
-
-
The DELL Support call center is in India. I heard this from more than one rep when I got my new DELL machine in August, 2019 and I wanted to be sure that it was up-to-date with drivers, BIOS/UEFI, etc.
Who knows … telling me that would save them a lot of work in checking to see if I had up-to-date drivers … at the time DELL’s Support Assist app was not working well {it does a better job now and I have installed the DELL UPDATE utility, as well, as a check on Support Assist}.
Nowadays, you can go to the DELL support website, type in your service tag number, click on Drivers & Downloads tab, and ask it to “detect drivers”. It will come back with a report of the driver updates you need and will send that info to the Support Assist app on your machine. Then you can open the Support Assist app on your machine and the driver updates will be waiting there for you to download and install.
Alternatively, you can open Support Assist on your device (without first going to the DELL Support website). If you click on the Drivers & Downloads option there, you will learn if any new drivers have been released for your machine. You can set the Support Assist app in Win10 to notify you if Support Assist has, on its own, found any new drivers for you. This way you get an automatic notification in the Win10 Action Center that there are new drivers for your machine. I haven’t set an app notification, though, because when you click on the notification to open Support Assist, Support Assist will perform all of the options, including optimization — which includes cleaning out the recycle bin. I don’t want my recycle bin automatically cleaned like that, so I just put it on my calendar to check Support Assist monthly.
And a warning: on opening Support Assist, if you do not want all four options to execute (and have your recycle bin cleaned out), click on the down arrow at the bottom of the splash screen, instead of clicking on the “Start Now” button, which will run all four options, after which you will end up with an empty recycle bin. {It took me a while to figure this out}
So, DELL has recently improved its support of your machine so that you get up-to-date OEM drivers, when they are released. And, consequently, you can ignore Microsoft driver updates.
1 user thanked author for this post.
-
-
-
I’m particularly grateful for PKCano’s contributions. My position — as a 1903 user updated 3 Feb. 20 — is that, frankly, life is much too short. I’m just running my laptop doing my thing(s). a) I don’t have the time to mess with enormously energy- and time-consuming incompetent MS update [edited]; and b), much more importantly, right at the beginning of this mess I suffered two catastrophic breakdowns/crashes caused by the Windows 10 Fall Creator nonsense. And I mean catastrophic: the first took four whole days to sort out; the second, another two days of my life (shorter only because I insisted the MS tech I was in touch with repeated the ISO upload). No way am I going to risk repeating that horrendous experience. Windows 10 is supposed to be an OS, not an excuse to pander to whatever idle time-wasting ‘up-whatevers’ someone at MS has dreamt up. So, I’ll take the original advice to pause updates, hoping new patches will compensate for the mess. Meanwhile, I live in hope that some millionaire user will go to the trouble of suing MS for incompetence.
-
Within the last two days, I have upgraded two of my Win10 Pro 1809 machines to Win10 1909 Build 18363.657 (Feb updates). The 1809 machines were current (up to date) through the Feb updates.
+ I started with an image backup.
+ Then I checked with wushowhide to be sure there were no pending updates I did not want to install (drivers and microcode, in this case). I hid them, then cleared the WU queue using the procedure in AKB2000013.
+ After the reboot, with WU reporting “up to date,” I set the Feature deferral to 80 days.
+ Then I again checked wushowhide to verify that the Feature upgrade to 1909 was all that was offered.
+ At this point, I had two options: I could wait until Win checked for updates again on its own, OR I could click “Check for updates” knowing Feature update to 1909 was all that was pending in wushowhide and there were no other updates showing in the queue in WU.
+ I chose the latter. I clicked “Check for updates” which initiated an immediate download/install process.One machine completed in a little under 2 hours. The other took quite a bit more time. But both were successful with no profile problems.
1 user thanked author for this post.
-
-
-
-
Having just finished with my buddy’s Win 7 machine, am reporting the following.
MSRT & preview were offered & hidden.
Check for new updates. No SSU was offered.
Feb.Cumulative Security Update for Internet Explorer 4537767 was downloaded from the catalog.The IE install completed as usual. Restart finished. Final check on windows updater said the PC was up to date. Checked history & there it was. Fail.
Suspicion confirmed. Non-ESU customers can download from the catalog & will be met with an eventual failure.
So long M$. Thanks for all the fish. End report.
Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler
-
I have just updated a Win10 Home x64 v1903 laptop with Feb’s updates. After 2 hours and a reboot, it gave me a blue nag screen about the MS account (which is not switched on).
I have not seen that before and I declined!
1 user thanked author for this post.
-
-
I just installed all updates on my Win10 v1909 home edition without a problem. I found it interesting that everything installed except KB4535996 which is sitting my optional updates queue. I’m going to release until MS-DEFCON gets lower than 3 or someone finally confirmed that KB4535996 is safe to installed. blueboy714
Custom Build - Intel i5 9400 5 Core CPU & ASUS TUF Z390 Plus Motherboard
Edition Windows 10 Home
Version 22H2Dell Laptop - Inspiron 15 11th Generation Intel(R) Core(TM) i5-1135G7 Processor
Edition Windows 11 Home
Version 23H2 -
I’m still with Windows 7 and decided to check for updates and see what would show up. In addition to the expected Malicious Software Removal Tool another important update appeared: KB915597 – Security Intelligence Update for Windows Defender Antivirus. Never seen anything like this before come through. Is it safe to install?
1 user thanked author for this post.
-
Never mind – this is apparently the virus definition updates. Usually have kept them current by downloading manually so hadn’t seen them come thru with the monthly updates before.
1 user thanked author for this post.
-
-
-
If you still have quality updates deferred for 30 days as before, that’s working correctly.
There were only 28 days between February patch Tuesday and March patch Tuesday.
1 user thanked author for this post.
-
Viewing 72 reply threads
Plus Membership
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Get Plus!
Recent Topics
-
No Newsletters since 27 January
by 8 minutes ago
-
Linux Mint Debian Edition 7 gets OEM support, death of Ubuntu-based Mint ?
by 29 minutes ago
-
Windows Update “Areca Technology Corporation – System – 6.20.0.41”
by 1 hour, 38 minutes ago
-
Google One Storage Questions
by 2 hours, 49 minutes ago
-
Button Missing for Automatic Apps Updates
by 20 minutes ago
-
Ancient SSD thinks it’s new
by 6 hours, 48 minutes ago
-
Washington State lab testing provider exposed health data of 1.6 million people
by 10 hours, 48 minutes ago
-
WinRE KB5057589 fake out
by 4 hours, 7 minutes ago
-
The April 2025 Windows RE update might show as unsuccessful in Windows Update
by 16 hours, 59 minutes ago
-
Firefox 137
by 1 hour, 36 minutes ago
-
Whisky, a popular Wine frontend for Mac gamers, is no more
by 23 hours, 11 minutes ago
-
Windows 11 Insider Preview build 26120.3863 (24H2) released to BETA
by 23 hours, 23 minutes ago
-
Windows 11 Insider Preview build 26200.5551 released to DEV
by 23 hours, 25 minutes ago
-
New Windows 11 PC setup — can I start over in the middle to set up a local id?
by 16 hours, 31 minutes ago
-
Windows 11 Insider Preview Build 26100.3902 (24H2) released to Release Preview
by 1 day, 2 hours ago
-
Oracle kinda-sorta tells customers it was pwned
by 1 day, 8 hours ago
-
Global data centers (AI) are driving a big increase in electricity demand
by 1 day, 19 hours ago
-
Office apps read-only for family members
by 1 day, 21 hours ago
-
Defunct domain for Microsoft account
by 1 day, 18 hours ago
-
24H2??
by 1 hour, 20 minutes ago
-
W11 23H2 April Updates threw ‘class not registered’
by 1 day, 3 hours ago
-
Master patch listing for April 8th, 2025
by 7 hours, 40 minutes ago
-
TotalAV safety warning popup
by 18 hours, 13 minutes ago
-
two pages side by side land scape
by 3 days, 19 hours ago
-
Deleting obsolete OneNote notebooks
by 3 days, 21 hours ago
-
Word/Outlook 2024 vs Dragon Professional 16
by 3 days ago
-
Security Essentials or Defender?
by 3 days, 3 hours ago
-
April 2025 updates out
by 54 minutes ago
-
Framework to stop selling some PCs in the US due to new tariffs
by 2 days, 20 hours ago
-
WARNING about Nvidia driver version 572.83 and 4000/5000 series cards
by 2 days, 10 hours ago
Remembering Woody
