If you’re running Win8, 8.1, 10 or related Server versions, stay on MS-DEFCON 2. Don’t install this month’s patches just yet. But if you have: Windows
[See the full post at: MS-DEFCON 3: Get Windows XP, Win7 and associated Servers patched]
|
There are isolated problems with current patches, but they are well-known and documented on this site. |
-
MS-DEFCON 3: Get Windows XP, Win7 and associated Servers patched
- This topic has 319 replies, 75 voices, and was last updated 4 years, 3 months ago.
AuthorViewing 101 reply threadsAuthor-
-
exceptional circumstances require action.’Rock and a hard place’ for Woody. IIRC this is the FIRST time OSes have been segregated for patching according to the MS-DEFCON level.
No problem can be solved from the same level of consciousness that created IT- AE -
-
-
Yes. There are caveats, discussed in the article, but the threat is very real.
IMHO, you’re better off patching now and picking up the pieces later, if need be. It’s been years since I’ve said that, but this situation’s potentially dire.
-
-
-
-
The information IS there – or just trust me for now. I don’t have time to look it up for you.
UPDATE: The first information on the pciclearstalecash file I have is it was bundled with the April 2018 Monthly Rollup KB4093118 delivered through WU – that will give you something to go on for searching.
1 user thanked author for this post.
-
-
-
Here’s some additional information… a search of the Registry for either of the strings below came back empty after running the update with both files located in the same folder on 5/15/2019…
pciclearstalecache
SlotPersistentInfoHowever… I noticed that the pci.sys file itself in the System32\Drivers folder changed after running the update! Here’s what changed for both 32 and 64 bit Windows 7.
BEFORE running the update the date modified on the pci.sys file was 2/10/2018 and the file version was 6.1.7601.24056.
AFTER running the update the date modified is now 4/18/2019 and the file version is now 6.1.7601.24441.The only difference I see between 32 bit and 64 bit is the file sizes. 32 bit has a file size of 150 kb and 64 bit’s file size is 180 kb. NOTE: These file sizes are noted from the file’s Properties – NOT the file size that shows in Windows Explorer.
1 user thanked author for this post.
-
-
-
-
-
@Ed:
When we ran that pciclearstalecache.exe in 2018, you could look in Windows\Logs to see that the “date modified” had changed to the current date (or rather, the date it ran) for the PCIClearStaleCache.txt file. That’s how we could tell it had run then; don’t know if that’s the case this time.Linux Mint Cinnamon 21.1
Group A:
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux, mostly offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux -
Same here, mine is dated 5/10/2018 which is the same date other updates show were installed in my update history.
My thoughts are either the file in the Logs folder should have been replaced with a new one or the date/time stamp should have changed. I’m also wondering if KB4499175 showing in the update history as successfully installed equates to BOTH processes completed successfully?
I still have 15 more computers to run these updates on and I’m holding off on all of them until I find out how to verify the process actually went as it should. I just finished running the April updates on all of these systems a couple days ago and I certainly don’t want to re-visit these 16 computers a third time because this didn’t work!
1 user thanked author for this post.
-
-
-
-
-
“Bundled with” does not mean a part of, it means included with. There are two files. Please follow the link and read about it.
1 user thanked author for this post.
-
-
Windows XP had/has a completely different patching system addressing issues. With Win7 through to W10, this all changed in October 2016 where individual patches were rolled-up in SO (Security Only-from the MS catalog) and SQMR (Security Quality Monthly Rollup from Windows Update).
I do believe there are ways to break them apart but, there are also caveats in doing so and I certainly would not recommend it.
No problem can be solved from the same level of consciousness that created IT- AE1 user thanked author for this post.
-
So are you recommending that we install all of May’s patches….including the Monthly Rollup, NET patch and all office patches? Windows 7 Group A here!
1 user thanked author for this post.
-
At this point, as mentioned in the article, install all available checked Win7 patches (.NET, Office, too), particularly including the Monthly Rollup.
I figure that’ll reduce your chances of hitting a bump in the road.
-
It seems to me, after 4 months of not patching (from January to April), that I will finally be patching my Windows 7 and 8.1 systems this month. That “wormable” vulnerability seems to be quite serious.
Just not now. No, I am not doing it now, not until I know what kind of problems to expect from the Windows 7 May patches. I don’t trust Microsoft’s track record on these patches.
I am running Windows 8.1 and MacOS Sierra / High Sierra in addition to Windows 7, and I believe I can afford to wait and see. I disabled Remote Desktop on every one of my Windows computers and I don’t think I am affected, even on Windows 7.
Hope for the best. Prepare for the worst.
2 users thanked author for this post.
-
-
I believe I can afford to wait and see. I disabled Remote Desktop on every one of my Windows computers and I don’t think I am affected, even on Windows 7.
You would think so, wouldn’t you? It’s a reasonable conclusion. But I can’t find one, single statement from a Microsoft employee who’s willing to reassure folks that way.
Like I said, there are many unanswered questions.
3 users thanked author for this post.
-
And if you have Windows 7 Home, it doesn’t come with RDP functionality anyway, so if you didn’t install additional software to enable it, it’s already off.
Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon (and Win 11 for maintenance)2 users thanked author for this post.
-
It’s possible that Windows 7 Home Premium is affected as well since it does have Remote Assistance, which is a limited/restricted version of RDP, and likely uses most of the same back-end.
1 user thanked author for this post.
-
-
-
JamesBond I agree. I will be waiting a few days too. We have “remote anything” turned off in the Services (disabled).
So Woody, 1. can we be affected if the service is off? 2. I assume … the Security Only (SO) patch for May will have the patch just the same as the full monthly patch, correct?
Thank you.
Windows 7 64bit Group B
1 user thanked author for this post.
-
-
-
I would like a comment from Woody on “if the service for remote is disabled. is one still vulnerable?”
Excellent question. I would think so – but I don’t know.
The problem is that the bug appears to be in something that’s a precursor to RDP authentication. Microsoft hasn’t given us enough information to say, definitively, that turning off RDP or blocking the RDP port, will also block the vulnerability.
Unless MS comes out and says something official, I have no way to verify the hypothesis, one way or the other.
-
-
For the record: Windows 7 Professional, Intel-based, no anti-virus other than Defender / Windows Firewall. Group A. Installed all “Important” updates that were offered and checked, which were three or four related to Office, the monthly rollup, a .NET rollup, and Defender definitions. (I skipped the virus scanning tool.)
The installation proceeded with no abnormalities and so far everything is working as expected. It’s a bit early yet, but I’ve run a few programs so far as experiments and the system appears to be fine.
-
Thanks @seff link helps:
https://support.microsoft.com/en-us/help/4499164/windows-7-update-kb4499164
No problem can be solved from the same level of consciousness that created IT- AE1 user thanked author for this post.
“If you’re running Vista, hang tight”. I am doing just that in respect of a Vista machine (yes, some are still in use!) and I hope that Microsoft will quickly rectify their omission. The last time they issued a critical XP patch they did remember to issue one for Vista as well.
1 user thanked author for this post.
-
-
-
The first thing to do, I recommend that you go to this thread in the Microsoft Answers forum and follow the instructions there. The biggest benefit you’ll get is that your wait for the Windows Update service to find updates will get considerably shorter.
A couple of weeks ago I put into service a Vista x86 for Business system, starting from scratch, and while the first couple of hundred updates sailed through, almost as soon as I installed Service Pack 2 the process of finding updates got as slow as molasses. Installing the updates listed in that post brought WU back to a normal speed.
Once you do that, you should be able to find and install updates newer than 2016 without much trouble.
I would then refer you to this other MS Answers thread, which lists certain post-EOL patches released for Vista that will not be available via WU.
Once you’re done with these patches, you might want to consider bringing your Vista laptop closer to current by applying updates for Server 2008. But first things first.
1 user thanked author for this post.
-
Sorry for the late reply. I followed your recommendations and was able to download 77 updates from MS after applying the five “speed up” patches. I then installed the five Shadow Brokers exploits patches. Everything went smooth! Thank you very much!
Now, about those Server 2008 patches…….
1 user thanked author for this post.
-
-
Once again, sorry for the late reply I got sidetracked with an Acer TravelMate 300 XP SP3 tune up. What a nightmare. I managed to get the XP fully patched but ran into problems when trying to fool Update to think it was XP SP3 embedded (POSReady) with a registry hack in order to get more recent updates. Windows Update downloaded 130 patches, but failed to install. No code given, but said to see install history (not available in XP). I tried to undo the hack but nothing, even going back to a previous restore point, helped. So I just turned off automatic updates. The laptop is also saddled with MSSE which won’t update and can’t be uninstalled, so I just added the legacy Malwarebytes v3.51 (which found 14 PUPs), so obviously the machine has been attacked. Don’t know what else I can do for it. I installed the last browsers; Chrome 49, Firefox ESR52, and IE 8.
Now, back to the Vista machine. When I told the customer she owed me $60 for what I had already done, she didn’t want to spend any more so I’m not going forward with the Server 2008 patches. I have already spent way too much time and effort for the $60.
I would like to thank you very much for the assistance you have offered. I would not reject any suggestions on the XP either.
1 user thanked author for this post.
-
-
-
In Win 7 patch “May 14, 2019—KB4499164 (Monthly Rollup)” is not mentioned “CVE-2019-0708 (Remote Desktop Services Remote Code Execution Vulnerability)”.
So fix is not present?
2 users thanked author for this post.
-
For more information about the resolved security vulnerabilities, please refer to the Security Update Guide. (from KB4499164)
So you can be sure by reading the Security Update Guide for CVE-2019-0708
Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge
1 user thanked author for this post.
Windows 7 Pro…Group A…Just finished installing May updates and so far so good. (Knock On Wood )
Update: Windows explorer has failed to start, looking for a solution or something to that effect. It then started okay.
This is the first time I have seen this on this computer. Will continue to monitor and see if it persist, and if it does, I will let everyone know. May or may not be a buggy update.
-
Just did the May updates on my laptop – Win 7 Home, Group A. All seems fine, though a bit sluggish. I haven’t seen any issues. Will restart again and see if all remains well. If it is, I’m going to go ahead on my desktop – also Win 7 Home, Group A. Fingers crossed!
-
Hello LHiggins, Two things I do with every MS update session is to Reboot SEVERAL times and let it sit for several minutes. On the last reboot to go to the desktop and let it sit 45 to 60 minutes to “Process Idle Tasks” and let the trusted installer (as per PKCano) run if needed.
It takes at least 20 minutes for the computer to realize you are not using it. If you notice the hard drive light flashing after that, it is “Process Idle Tasks”. Leave it alone (and not go to sleep) until the drive light stops flashing wildly, then reboot again since part of the “Process Idle Tasks” is to reorganize the startup file order.
Hope this helps.
Windows 7 Group B
-
-
@LHiggins-
A more precise way of seeing if Window Updates have completed their mission is by opening the task manager, and checking CPU usage after the first reboot, and waiting until it drops below 10% before doing anything else. Rebooting again, before that, simply interrupts the process.
I’m not sure why you would be doing multiple reboots for updates routinely?
Non-techy Win 10 Pro and Linux Mint experimenter
-
Hello Elly, nice to talk to you again. Elly your idea is a good one of looking to see if any behind the scenes ‘Idle Tasks” are presently running. For the last few years I and others I deal with will install the MS patches one-by-one, with a reboot after each. I notice my computer runs odd after MOST of these MS updates. I then reboot the computer 2, 3 or more times until is seems to act more normal. I had one poster disagree and say this will all happen eventually with time. Yes, that is true, but I want my computer running properly “right now” (in 20 to 45 min) not in a few days.
The other reason for the reboots is that the computer forces processes (install processes) to end/finalize and get written to disk, forces the registry to write to disk (hopefully before a blue screen happens) and recover normal operation faster. The 45 minute sit idle finishes any leftovers.
I would also recommend people run disk defragmenter on a rotating drive and TRIM (optimize) on an SSD. (Note here at Woody’s there was a discussion of SSDs now being far superior to those of yesteryear and it was OK to run Disk defragmenter on these new drives. Some still say NO some say YES.) https://www.askwoody.com/forums/topic/langalist-i-know-to-de-fragment-my-hdd-and-not-to-de-fragment-my-ssd-do-i-de-fragment-my-hybrid-drive
Thank you.
-
Hello again LHiggins, the “rest” or idling afterwards is good. One item I forgot to mention was this month also has .NETs to install. Whenever a .NET is updated or installed, it then needs to run MSCORSVW to rebuild or consolidate the .NET image. his takes time and even though MS says it is transparent, one can feel the sluggishness it produces.
If you or others here are interested, one can run the MSCORSVW .net image compiler (NGEN) manually. http://blogs.msdn.com/b/dotnet/archive/2013/08/06/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up.aspx
Hope this helps.
Windows 7 Group B
-
-
Hello again LHiggins, every now and then I hear of an odd CPU issue with that which is the INDEX feature of Windows. On some machines we have it off on others it was left alone.
You might want to investigate resetting or forcing a rebuilding of the index.
https://www.winhelponline.com/blog/reset-rebuild-windows-search-index-fix-problems/
Way back in 2013 people were complaining of this in the MS forum and some said that fixed them.
Hope this helps. Let us know if it does or not.
Windows 7 Group B
-
-
Hello LHiggins, Hope things are going better for you. ” Could it have been re-indexing everything after the MS Updates?” Possibly. I am not an indexing expert. Like I said we have it off on some computers and left alone on the ones that didn’t give us any troubles. I would leave it on if you can. Someone like NOELC might want to comment.
“A question – I had read that I can change the indexing options so that it doesn’t index everything. Is that a good idea?”. Again it is up to you on how you use your computer. How often do you have it look for a file? If you very seldom have it look then maybe turning off or adjusting the indexing to suit you would be better. If you do search for files regularly, then maybe the defaults are best. See,
https://www.howtogeek.com/272158/how-to-choose-which-files-windows-search-indexes-on-your-pc/“On my laptop, the memory usage is usually between 60-70% but the CPU isn’t usually very high – 10-15% depending on what is running.” This appears to be straining. If you could add ore RAM that would help. 10-15% is OK if something is actually running you want. If it is always hovering at 10% then why? It should go to 1-2% when truly idle.
“On the desktop, memory usage is generally between 15-20%, and CPU is pretty low unless something is actually running – right now, 0-1% while it is “idling”. This sounds very good.
Windows 7 Group B
1 user thanked author for this post.
-
-
-
-
I was curious if there is a lounge thread on how people are going about disabling remote desktop. So far i’ve disabled remote desktop services within services and i always have the option ‘allow remote assistance connections to this computer’ unchecked.
1 user thanked author for this post.
-
Hello T, one thing is to turn off remote access by removing the check.
https://www.lifewire.com/disable-windows-remote-desktop-153337
Another is to go to services.msc and go down to Remote Desktop Services and disable that services (be careful!) and any others that deals with remotely accessing your computer, such as Remote Registry.
While you are there if you are on Windows 7, do you need to have error reports? If you feel you don’t consider disabling “Windows Error Reporting”.
Do not disable services unless you researched them first. A service may be needed but look bad to you in its name.
Hope this helps.
Win 7 Pro x64, Group B. Did the SO as instructed, IE11 and SO .Net 4.6.1, then fired up WU and hid the rollups and updated Defender and two Office 2010 updates before shutting off WU again. Nothing is smoking. Suppose I should be grateful for small mercies…
I have RDP turned more or less permanently off (except when I need to swap files between it and my Mac) and, with the alternatives to Windows I have obtained already as a precaution (and, with no known evidence to the contrary, I must assume they are OK already after their very recent patching — cross my fingers), given the near-future EOL of Windows 7, I am also keeping my home Windows PC off the Internet for a few more days, to have some time to see how things develop. But, with the limited information available, what is the best way to ensure safety within any given situation (users of home, small business or corporate computers) still cannot be decided based on the still not entirely clear information available from MS (something that Woody has pointed out in one of his entries here). So, good luck to all of us!
Group B Windows 7 Pro, SP1, x64 + macOS & Linux Mint.
Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).
MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV1 user thanked author for this post.
Windows 7 64-bit, Group A. Updated and all seems OK (so far…) But — as now seems to happen more months than not — Windows Media Player has to be re-configured. An annoyance, but a minor one since all options/settings are retained except for how often to check for updates.
-
I agree, this is not needed and IMO, this is borderline harassment for having Window 7. I don’t have to reconfigure it every time I update my Windows 10 computer.
1 user thanked author for this post.
I installed kb4499406, kb4499164 and kb890830 and all went well. Came over here to post, clicked on the main title and the running conversation was no where to be seen. Clicked on recent replies and all could be seen. Anyone else have that surprise?
Edition Windows 11 Pro
Version 22H2
Installed on 10/19/2022
OS build 22621.2283I’ll rely on my security suite and common sense, haven’t patched since Dec 2017
1 user thanked author for this post.
I have around 40 windows 7 machines that I’ll be pushing KB4499164. If I run into anything I’ll let you know. All the other May updates are on hold except for the flash updates. I still need to take a closer look at the .net patch with the issue. I’ll give that a couple days to see if any problems are reported.
Red Ruffnsore
Does this apply to Windows Home Server?
1 user thanked author for this post.
The MS information page for the Win7 monthly rollup KB4499164 is reporting problems with McAfee.
You know, I’ve been thinking about the different AV not playing nice with Windows 7 rollups, updates, etc. ie last month’s AV that were having issues, and now McAfee….
I have MSE for my AV and so far, knock on wood, no problems.
It would be interesting to find out if anyone with MSE is having issues.
My money is on “no” they are not.
Having said that,
Is MS messing with all the other AV’s that run Windows 7 because they don’t want them to work anymore with Windows 7?
I’m on the fence about continuing to keep W7 after EOL but was wondering what AV I could use.
TBH, I don’t really trust MS with anything Windows 7.
My RDP has always been off.
I think I’m going to hold off a couple of days and stay tuned here to see what issues may or may not be reported.
Years ago when I had XP and they wanted people to upgrade,
I always felt that an update is what bricked my computer.
I’m feeling this is a dejavu.Dell Inspiron 660 (new hard drive installed and Windows 7 reloaded Nov. 2017)
Windows 7 Home Premium 64 bit SP 1 GROUP A
Processor: Intel i3-3240 (ivy bridge 3rd generation)
chipset Intel (R) 7 series/C216
chipset family SATA AHCI Controller -1 E02
NIC Realtek PCLE GBE Family ControllerMSE antivirus
Chrome browser1 user thanked author for this post.
Windows 7-64 Professional SP1 on Intel DX58SO2 motherboard and i7-960 CPU, 12 GB Ram, nVidia GTX 660Ti SC (3MB) and spinning HDDs, wired network, no wireless or bluetooth, no overclock. Home built.
Patching as Group B, installed May 2019 Security Only and IE patches, no issues. Single reboot after each. Installed .NET updates via WU, no issue (required reboot). Office 2010 patches and MSRT installed via WU. Sitting at a walnut desk with knuckles knocking on wood, no issues so far after 2 hours. The installs seemed to take the standard amount of time. No flash of a CMD window from the pciclearstalecache.exe part, but that had been installed before.
I see no loss of performance at this time.
Hope this helps.
I intend to install the XP patch from the Catalog on the offline XP machine just in case I go online, but for now it remains offlime.
Installed KB890830-MRT, Rollup for .NET KB4499406, Rollup for Win 7 KB4499164;
No issues so far, but it’s early. (Whew)
(BTW, heckuva time for one of my backup drives to act goofy…but you all know the label on the machinery hatch cover: “In order to ensure malfunction, set clamps on all hatches, seal tightly, connect all cables, and start process.” Or, “Whaddya mean, we have no flaps??“)
Win7 Pro SP1 64-bit, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Greenhorn
--
"Nine out of 10 doctors say Acid Reflux is mainly caused by computers."I’m going to wait a bit. My employer hasn’t patched my Windows 7 workstation yet.
The last time I pushed ahead and updated my home computer first was during the March 2018 update disaster, where I ended up having to uninstall the March patches before I could install the April ones. My employer did the right thing and bypassed the March updates entirely.
I expect they’ll push out the 2019-05 patches tomorrow or Friday.
I suggest that if you don’t NEED it, just don’t expose your Remote Desktop interface to the world wide web.
Just disable it (you may never have ENabled it; it’s not enabled by default). This is from memory: Right-click on My Computer, choose Properties, Advanced system settings, Remote tab. Look in the Remote Desktop section.
Home router between your system and the internet? Great! That’s an extra layer of protection since it normally – unless you’ve reconfigured it – will block incoming connection requests from reaching your computer. With almost all NAT type routers, you’d have to set it to pass ports through or set your whole computer to be in the DMZ in order for connection attempts to reach your computers on the LAN side at all. Don’t do that!
-Noel
15 users thanked author for this post.
-
There is something called Remote Assistance that is by default enabled (on Windows 7 Home Premium, at least.) I believe that still works using RDP. It should also likely be turned off. (It is found in the same place you described, under the Advanced System Settings > Remote Access.)
That said, I was curious why being behind a NAT was not being mentioned. I could not figure out how something was supposed to get in that isn’t a part of my network. Unless there is some way to exploit this by my going to a webpage (or otherwise making an outbound connection), I don’t see how it could get in.
-
UPDATE: I’ve now seen one reliable report that there’s an RDP exploit in the wild. The attacks are said to come from China.
I’m serious, folks. If your machine is connected to the internet, you need to install this patch.
I updated four Windows 7 computers – Group B: two are 64 bit Home, one is 32 bit Home and one is 32 bit Pro.
4499175, 4498206, 4495612 and one computer also 4495593.
I run MS Security Essentials and malwarebytes Pro.
No problems on any computer but I always image before I update and I didn’t skip it this month.
Got coffee?
Installed Rollup KB4499164, Office 2010 KB4464567, MSRT KB890830, .NET Framework KB4499406. I always keep “give me recommended updates the same way I receive important updates” UNCHECKED. My Win7 machine is sitting at a nice idle with Norton performance tasks running in the background. After updating I let it sit for about an hour then ran a few programs, got on some websites I frequently visit, and it all seems to be holding steady with Chrome and common tasks. Haven’t noticed any slowdown after shutting down and powering up again a couple of times. So far it’s all good, thanks Woody, PK, for guidance, and to everyone who piped in with results and feedback. You all make this site a lifesaver for IT types, home users like myself, and companies operating on trust and efficiency. You’re the best!
MacOS, iOS, iPadOS, and SOS at times.
Win7 Home Premium, 64-bit, Group B.
I installed the two msu’s today (with the new pciclearstalecache .EXE file in the same folder), and so far everything seems to be fine.
I went to Services and found that both Remote Desktop Configuration and Remote Desktop Services were set to Manual — so if they’re both Disabled by default, and I had to guess, I’d guess maybe those settings got changed a few years ago when I let Norton support take over my PC.
In any case, I’ve now changed the Startup Type for both services to Disabled.
First time I’ve ever posted although I’ve been reading the various incarnations of the newsletter since about 1997/98. Anyway, FWIW, I was able to install the Win 7 rollup and Net rollup and everything seems to be working fine. I have Win 7 Home Premium. The Net rollup took a few tries (got error 80070020). Googled the error then followed a recommendation to install in safe mode with networking, which didn’t work. I tried it one more time normally and it worked that time. My version of Office is too old so I don’t get those updates.
Edit: Removed HTML
KB4499164, KB4499406 & KB890830 downloaded and installed slick and quick with a shiny new SSD on a 5 year old ZBook. As is my customary practice, patches applied/rebooted individually. All tickety-boo so far. Thanks Woody and all the MVP’s for the timely heads up. Win 7 Pro, x64 SP1, i-7core “Haswell” Grp. A.
Decided to do an experiment on one of my old machines used by my father (AMD FX-8320 CPU / 880G motherboard) to see if the 2019 updates cause any problems, and to familiarize myself with the procedure if I decide I need to patch my Windows 7 systems.
The system was patched to December 2018 level, Group B style. I installed the 2019 updates on that machine in the following order :
KB4480085 (.NET 3.5.1 Security-only update Jan 2019)
KB4480076 (.NET 4.5.2 Security-only update Jan 2019)
KB4480960 (Security-only update Jan 2019) Reboot
KB4487345 (Fixes for KB4480960) Reboot
KB4483483 (.NET 3.5.1 Security-only update Feb 2019)
KB4483474 (.NET 4.5.2 Security-only update Feb 2019)
KB4486564 (Security-only update Feb 2019) Reboot
KB4490511 (Fixes for KB4486564) Reboot
KB4489885 (Security-only update Mar 2019) Reboot
KB4474419 (SHA-2 update) Reboot
KB4490628 (Servicing Stack update)
KB4493448 (Security-only update Apr 2019) Reboot (Twice)
KB4495612 (.NET 3.5.1 Security-only update May 2019)
KB4495593 (.NET 4.5.2 Security-only update May 2019)
KB4498206 (IE11 Cumulative Security update May 2019) Reboot
KB4499175 (Security-only update May 2019) RebootThe system so far seems to run without problems. Will continue to monitor. If necessary I can revert to the December 2018 image using Acronis True Image.
As for my other systems, they are running both Windows 7 and Windows 8.1 (and MacOS Sierra / High Sierra), and I can use Windows 8.1 at this time while monitoring for any problems associated with the May 2019 updates. Will continue to wait until I decide it is time to patch.
Hope for the best. Prepare for the worst.
-
-
See the procedure here for pciclearstalecache with the Security-only patch this month.
1 user thanked author for this post.
-
-
@woody not sure what your advice is for Vista users but some folks here have asked about Vista concerning CVE-2019-0708. Found info on BornCity posted yesterday, https://borncity.com/win/2019/05/15/critical-update-for-windows-xp-up-to-windows-7-may-2019/
Noted as follows – “For Windows versions that have already dropped out of support, the user must download the update himself. Users of Windows Vista can download the updates (Monthly Rollup or Security Online) of Windows Server 2008 from the Update Catalog and install them manually.”MacOS, iOS, iPadOS, and SOS at times.
3 users thanked author for this post.
-
It worked for me.
ASRock Beebox J3160 - Win7 Ultimate x64
Asus VivoPC VC62B - Win7 Ultimate x64
Dell Latitude E6430 - Win7 Ultimate x64, Win10 Pro 22H2 x64 (multiboot)
Dell Latitude XT3 - Win7 Ultimate x86
Asus H170 Pro Gaming - Win10 Pro 22H2 x64
Born’s Tech and Windows World
For Windows versions that have already dropped out of support, the user must download the update himself. Users of Windows Vista can download the updates (Monthly Rollup or Security Online) of Windows Server 2008 from the Update Catalog and install them manually.
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0708
Updated my VISTA 32, from the MS CATALOG
https://www.catalog.update.microsoft.com/Home.aspx
INSTALLED. OK !1 user thanked author for this post.
-
For me it also worked to manually install the Server 2008 security only update (KB4499180) from the catalog on my Vista x86 system. The rollup (KB4499149) did not work, it got stuck at 50% when updating. I have not seen any issues, and will report when I do start seeing them.
I am usually quite hesitant to install updates from another OS. I tried this for the first time when Vista went EOL. I then installed Server 2008 updates for 2 consecutive months, but in the second month Outlook stopped working. I could reproduce that the Server 2008 updates were the cause for this, so I stopped patching Vista with Server 2008 updates, restored an image from right after Vista went EOL and have barely used the system since. I will still upgrade to Windows 7 and then Windows 10, that is why I keep the system alive. If I browse the internet I open a remote desktop to a Windows 7 machine and browse on that one.
ASRock Beebox J3160 - Win7 Ultimate x64
Asus VivoPC VC62B - Win7 Ultimate x64
Dell Latitude E6430 - Win7 Ultimate x64, Win10 Pro 22H2 x64 (multiboot)
Dell Latitude XT3 - Win7 Ultimate x86
Asus H170 Pro Gaming - Win10 Pro 22H2 x64 -
-
I do not know. I did find that the rollups for Server 2008 started somewhere in 2018, but I could not find if older updates are also included. I assume they do not include all updates since Vista went EOL, because that was April 2017. But I did want to try the rollup and as you’ve read it failed. If it was successful I would have had more security updates than just the May 2019 one.
ASRock Beebox J3160 - Win7 Ultimate x64
Asus VivoPC VC62B - Win7 Ultimate x64
Dell Latitude E6430 - Win7 Ultimate x64, Win10 Pro 22H2 x64 (multiboot)
Dell Latitude XT3 - Win7 Ultimate x86
Asus H170 Pro Gaming - Win10 Pro 22H2 x641 user thanked author for this post.
-
-
-
-
I have now tried to install KB4499180 for Server 2008 on my Vista Home Premium machine. It got part way into the updating process after restarting the computer but then produced a BSOD followed by a prompt to go into system repair mode, which restored things to their previous state (hopefully without any side effects). Be warned!
-
-
-
I have now done a manual system restore to the point before the failed update, disabled remote desktop and put a specific block on TCP port 3389. Unless Microsoft issue a Vista-specific patch, that is as far as I can go with this one.
2 users thanked author for this post.
-
A bit more detail about the failed update on my Vista Home Premium desktop machine (which I have just repeated to remind myself of the point at which it crashed): post-restart stages 1 and 2 of the installation completed OK, but the stage 3 restart failed. A pleasing thing about what happened is that the computer recovered so smoothly after crashing. It has been many years since I last had a BSOD on this very reliable machine.
2 users thanked author for this post.
-
-
-
I took the plunge and just finished installing KB4499149, the Monthly Rollup for Server 2008 SP2, on my Vista Home Premium SP2 laptop. Everything seems to have gone well, tried opening a few programs and they all worked. Also installed the mysterious “pcicompatforserialnumber” .EXE file that came along with it, for which I couldn’t find any information.
Before installing KB4499149, I installed the Servicing Stack Update for Server SP2.
FWIW, the installation order I chose was SSU, then pcicompatforserialnumber, and then finally KB4499149. A reboot was requested only after that last one.
While looking into these patches, I learned that monthly rollups for Server 2008 SP2 began in September 2018 and that each rollup includes every Windows patch that came before it, the same model as for Windows 7 Group A. Patching for Server 2008 SP2 ends in January 2020, just as for Windows 7.
1 user thanked author for this post.
-
See this procedure for Win7. I going to guess the .exe file you found installs the same way as pciclearstalecache does.
1 user thanked author for this post.
-
OTOH, after working to perfection on the laptop, KB4499149 failed spectacularly on my Vista tower: upon reboot, the machine went into a black screen with just the mouse pointer in the center; nothing that I did brought a display into view. Startup Repair didn’t help, in fact it even claimed it couldn’t find an operating system!
Had to use a Windows installation disk to System Restore to just before the patch was applied. After booting successfully into Vista, a visit to the Windows Update history showed that KB4499149 had “Failed.”
1 user thanked author for this post.
-
Hi cybertooth:
Is there any difference in the way you’ve applied the KB4499149 Win Server 2008 patches on your Vista SP2 laptop (successful) and desktop (failure)? For example, you mentioned in post # 1659353 you applied the April 2019 Servicing Stack Update for Win Sever 2008 and pcicompatforserialnumber.exe file before KB4499149 installed successfully on your laptop. Is that the identical process you followed on the desktop, and have you applied other Win Server 2008 updates on either of these machines since extended support for Vista SP2 ended on 11-Apr-2019?
Pim stated in post # 1637517 that the KB4499149 (Monthly Rollup) failed on their Vista SP2 machine but that the KB4499180 (Security Only) update installed correctly. Does anyone know if there are different prerequisites for these two May 2019 patches?
I haven’t taken any action on my Vista SP2 machine yet except to confirm that Remote Assistance (Control Panel | System and Maintenance | System | Remote Settings) is disabled. I’m still hoping that Microsoft will release an out-of-band patch for this Remote Desktop Services vulnerability (known as Terminal Services in older OSs) that is specifically targeted for Vista SP2 in the next few days.
————-
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.01 user thanked author for this post.
-
Yes, actually there was a difference in the way that I applied the patch to the laptop vs. the tower PC. @pkcano suggested skipping the manual execution of pcicompatforserialnumber, and this sounded reasonable so I did it.
I doubt, though, that that made such a dramatic difference. Here’s another data point: after the failure of KB4499149, I proceeded to install the Server 2008 SP2 patches for August 2018. (My machine was previously patched up to July 2018. Also, note FWIW that I’m on a 64-bit system.) There are six patches in my folder for that month’s updates. The first one, KB4338380,when clicked on reported that it did not apply to my system. The next two patches , KB4340397 and KB4340939, installed and required reboots that went fine.
However, when I tried to install the Spectre/Meltdown patch KB4341832 and rebooted, the machine appeared to start loading Vista… and then entered into a black screen with just the mouse pointer showing. This is the same behavior observed when I tried to install KB4499149. I suspect that this, and not skipping the pcicompaforserialnumber, is the reason for the black screen.
This is a bit of a problem, because Microsoft began implementing the Rollup model the very next month, September 2018. Rollups, of course, include every patch that’s come before them–which means that they include KB4341832 which cannot be separated out, so I can’t install the rollups on this machine.
I haven’t tried the Security Only update for September (still working on the August patches), but if I understand it correctly the SO is not cumulative so it won’t contain the problem patch KB4341832. Bottom line is that I’ll have to install each month’s SO instead of being able to catch up all at once with the Monthly Rollup as I did with the laptop.
1 user thanked author for this post.
-
Today I tried to install KB4499180, KB4499149 having failed last week. The result was the same: after visibly attempting to boot, with those rolling bars on the splash screen, Vista ended up at a black screen. The power button was lit, but all it took to turn the power off was to press it once, briefly. (Recall that when a computer is properly booted, in order to power-cycle it you typically need to keep the power button pressed for several seconds.)
So it looks like this Vista tower will, for whatever reason, not accept any major Server 2008 updates beyond August 2018. It does seem to be taking IE9 and .NET Framework updates OK, but not “Vista” (Server 2008) updates. It will have to rely on the machine’s Internet invisibility (“stealth mode” as described by Steve Gibson) for protection from that Remote Desktop issue.
Or I can complete my transition to Kubuntu Linux.
1 user thanked author for this post.
-
For Vista SP2 users who have experienced BSODs and other problems after installing a May 2019 Windows Server 2008 update (i.e., the KB4499149 Monthly Rollup or the KB4499180 Security Only update) to patch this Remote Desktop Services vulnerability (CVE-2019-0708), it might be worth noting that as of last month’s April 2019 Patch Tuesday the Windows Server 2008 patches will change the build number of Vista SP2 from build number from 6.0.6002.xxxxx (Build 2) to 6.0.6003.xxxxx (Build 3). This is a deliberate change by Microsoft – see the support article Build Number Changing to 6003 in Windows Server 2008 – but some users posting in Jody Thorton’s MSFN thread Server 2008 Updates on Windows Vista have noted that this change to build number 6.0.6003.xxxxx appears to be causing problems on their Vista SP2 systems.
————-
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0-
Now that Microsoft has officially declared the Server 2008 security update to be Vista-compatible, I downloaded KB4499180 again (as well as servicing stack update KB4493730 for good measure). These updates installed successfully on my Vista Home Premium machine. Presumably Microsoft changed something in KB4499180 to ensure a successful Vista installation this time.
1 user thanked author for this post.
-
-
@Cybertooth, After reinstalling Defender it has been sent back to 1.0.0.0 25/01/2006 and fails to update through the GUI (error code 0x80070643), Windows update, and with the manually downloaded mpas-fe.exe.
Before the latest patch KB4500331 was applied the defs were dated January 2019.
Win 7 updated with no problems so far and windows update on XP still works but Defender has bugged out.
1 user thanked author for this post.
-
-
-
Good question. Sadly, the answer is you should be OK — but we still don’t have official word from Microsoft.
The problem is that the bug shows up in RDP before the atttacker’s authenticated. It would make sense that turning off RDP would protect you. But I can’t guarantee it.
1 user thanked author for this post.
Running Windows 7 Home, I installed the recommended monthly rollup update (4499164) and after that also the Windows tool for removal of harmful software (KB890830).
Then Windows wouldn’t shut down. Perhaps I didn’t wait long enough. I rebooted several times – some of the times a blue screen came. I could start up alright. Then I uninstalled the monthly rollup update. But the problem didn’t go away.
Luckily I did an image backup before the Windows update (with Macrium Reflect), so I may have to revert to that. Unless someone has a good idea? (I have read suggestions about this and haven’t tried them all).
1 user thanked author for this post.
-
@JustAsking are you by chance using McAfee AV?
MacOS, iOS, iPadOS, and SOS at times.
1 user thanked author for this post.
-
-
-
JustAsking, upon reading your post I saw Malwarebytes Premium mentioned. We have a computer using that and it appears to be beneficial. However, about once a year we run into an issue where the computer is causing a problem. After much investigation we turn off the background process of Malwarebytes. Problem gone. We then look at the Malwarebytes forum and people mention similar and there is a denial of it being Malwarebytes. After about a week a new version of Malwarebytes comes out and the problem is gone. This has happened MORE than once to us.
If you get an answer to your blue screen, please let us know what it was.
-
-
Good question @willygirl
There have been reports that McAfee is experiencing problems with updates in Win7 again this month. There may be lingering problems with Win7 updates and the AVs affected last month.-
@pkcano saw this originally posted by @microfix
See above #1628248 via @microfix link posted https://support.microsoft.com/en-us/help/4499164/windows-7-update-kb4499164MacOS, iOS, iPadOS, and SOS at times.
1 user thanked author for this post.
-
I believe the mandatory date for SHA-2 is in July.
1 user thanked author for this post.
Windows 2003 and 2008 server updates and reboot went without a hitch last night except for Quest Desktop Authority script which needed to be resynced this morning.
Our Windows 7 desktops run updates in waves. Only a few in the first wave, I included, who are generally tolerant of issues. I pushed up the other waves, which I would normally not do this soon, to run last night at 3 am. Some did and some didn’t.
PC issues I’m working on today:
1) We use Quest Desktop Authority login/out scripting. Files on distribution servers became corrupt. Early birds who logged in got an error and no mapped drives. Resolved by resyncing to the distribution servers and sending a link to those users to click and run the script again.
2) For some, their Symantec client has firewall corruption issue. Rebooting twice resolved.
3) On those computers who should have installed Windows Updates last night, this morning I can’t access Windows Updates on those computers to confirm. WU is red and clicking check for updates give this error, “Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer.” WU is running. Restarting doesn’t resolve it. On a test computer (she’s out today; lucky her), I troubleshooted by stopping WU service, renaming SoftwareDistribution folder, and restarting WU. Check for updates runs but shows a long list of 34 updates I know were already installed. Grr. I’m hoping there’s something different I can do to fix that issue instead.
—–
Win7 SP1 Pro 64-bit; Office 2010; Symantec SEP 14.2 On-premise; Group A
Installed the May rollup KB4499164 on 2 Windows 7 x64 systems and so far no problems.
One system is Windows 7 Home Premium with Kaspersky and an old version of Malwarebytes; Malwarebytes wasn’t running while I installed the update. Let the machine sit for 30 minutes after the reboot and then turned Malwarebytes back on; so far everything seems to be OK.
The other system is Windows 7 Ultimate running Avast and the old version of Malwarebytes. Followed a similar procedure with it and everything seems to be running OK so far on that one, too.
Thanks to Woody and PKCano for the guidance and to everyone else posting here for all the helpful information. Good luck to everyone.
Linux Mint Cinnamon 21.1
Group A:
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux, mostly offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with LinuxUPDATE: I’ve now seen one reliable report that there’s an RDP exploit in the wild. The attacks are said to come from China.
I’m serious, folks. If your machine is connected to the internet, you need to install this patch.
Ok, after reading this post from woody………
took a deep breath and installed the May rollup KB4499164
Did not install the .net kb4499406….(not that brave yet)
Did not install MSRT (haven’t for several months now) and hid it
Install went smoothly and having no issues.
I’m adding my internet connection to my infoDell Inspiron 660 (new hard drive installed and Windows 7 reloaded Nov. 2017)
Windows 7 Home Premium 64 bit SP 1 GROUP A
Processor: Intel i3-3240 (ivy bridge 3rd generation)
chipset Intel (R) 7 series/C216
chipset family SATA AHCI Controller -1 E02
NIC Realtek PCLE GBE Family ControllerMSE antivirus
Chrome browser
DSL via ethernet (landline)FYI: the only thing I find is that this site is verrrrrrry slow!
Has been for a while now.Windows 7 x64 Home Premium Group A.
KB4499164 and .Net monthly rollups installed successfully. I just wanted to clarify that it is no longer necessary to manually disable the two Remote Desktop services given the successful installation of the monthly rollup.
I also do not understand why the pci-clear-cache executable was removed from the monthly rollup starting with last month. I assume that Microsoft removed it for valid reasons, and that I probably don’t need to understand the rationale given that I am in Group A. Was it removed by Microsoft because the NIC error that occurred around March, 2018 had been resolved recently?
1 user thanked author for this post.
Took Woody’s advice and went for it prior to the Def-Con baking cycle being fully completed for the “May” items.
Group A running Win7 PRO 32bit on an old Wolfdale version of Intel Core2 Duo in an HP dc7900 sff. I disabled my Norton Internet Security and then installed each of these one at a time and with about 45 minute wait after each install followed by a reboot. All went without any noticeable issues or sluggishness. Been back on the PC for about 2 hours without any hint of trouble.
1st on deck was the May RU KB4499164, followed by May .net KB4499406, and lastly the MSRT KB890830. After all these were completed, I reran the check for updates and found none (except for a couple optional that I ignored per standard protocol).
I ran the Disk Cleanup tools and then rebooted one last time after making sure TrustedInstaller was no longer showing in Task Manager.
1 user thanked author for this post.
-
FWIW, I’ve been using Norton, and manually installing Windows (and Office) updates, for many years, and I have never disabled Norton, and that’s never caused a problem. The risk of disabling the protection may be small, because you’re only disabling for a limited amount of time, but I’m inclined to think it’s a greater risk than the risk that not disabling Norton will somehow mess with the updates.
Don’t forget that Windows updates get installed automatically on most users’ PCs, so Norton clearly doesn’t get disabled when those updates are happening.
-
Windows 7 – 64 Home Premium with McAfee (home) Security Center provided by my ISP. I also have the latest Malwarebytes free. Group A.
I installed the cumulative and Net updates and the malware removal tool and haven’t had any problems including slowdowns.
—
As a side note: Askwoody.com has been a lot slower to load since the merger process and almost unreachable in the last day or two. But since the time the “test post” disappeared the load times have been quick. 🙂
-firemind.1 user thanked author for this post.
On a “test bench” that I setup (AMD 990 motherboard / Phenom II X6 1090T), I tried to run the May 2019 Rollup KB4499164 (previously has the December 2018 Rollup KB4471318 installed) to patch the system, but I was presented with a message that said something like “This update was not installed”. I tried THREE times and was presented with this message every time.
I tried to install it from Windows Update twice, and again the installation failed with the 8000FFFF error message, every time.
Frustrated, I then turned to the Security-only updates and installed them in the order in this post, omitting the .NET updates this time. And this time all the security-only updates installed successfully.
Edit : Now that I think about it again, I have neglected to install the Servicing Stack update KB4490628, which probably may have prevented KB4499164 from installing. But when I attempted the installation from Windows Update I don’t remember seeing that update being offered in Windows Update. Maybe I have to try it again and see if this is the problem.
Hope for the best. Prepare for the worst.
1 user thanked author for this post.
Hello LHiggins, Two things I do with every MS update session is to Reboot SEVERAL times and let it sit for several minutes. On the last reboot to go to the desktop and let it sit 45 to 60 minutes to “Process Idle Tasks” and let the trusted installer (as per PKCano) run if needed.
It takes at least 20 minutes for the computer to realize you are not using it. If you notice the hard drive light flashing after that, it is “Process Idle Tasks”. Leave it alone (and not go to sleep) until the drive light stops flashing wildly, then reboot again since part of the “Process Idle Tasks” is to reorganize the startup file order.
Hope this helps.
Windows 7 Group B
I disagree, and I disagree with with the last sentence in your last full paragraph. Windows bootup is divided into four stages. Everything which loads when Windows boots, loads under one of the following four sequences:
StartType=0x0 ; SERVICE_BOOT_START 0x00000000 (Anything set to 0x0 loads instantly after the kernel loads. OS uptime is the instant when the kernel loads.)
StartType=0x1 ; SERVICE_SYSTEM_START 0x00000001 (Low level drivers including AV drivers and backup utility drivers. These load immediately after all 0x0 has completed, and usually have completed loading during the first minute after zero OS uptime.)
StartType=0x2 ; SERVICE_AUTO_START 0x00000002 (Other services. These usually have completed loading within 5 minutes of zero OS uptime.)
StartType=0x3 ; SERVICE_DEMAND_START 0x00000003 (More stuff, such as programs which check for updates, Windows Update, or programs which you have chosen to launch via Startup. These usually have completed loading within 10 minutes of zero OS uptime.)
The upshot is that, unless there is something seriously wrong with your computer, then after 15 minutes, Windows 7 should be fully booted up and should be in a stable state with the hard drive activity LED flashing once per second.
Yet there is one thing which could possibly affect achieving this stable state: the Windows Disk Defragmenter. This bad puppy, if not correctly configured, can kick in after the 0x2 and 0x3 startup stages to cause a royal mess in terms the Win7 OS achieving a stable state within 15 minutes of OS bootup. My preference is to disable Disk Defragmenter in Task Scheduler and to instead manually run it when I choose to do so.
1 user thanked author for this post.
-
Assuming that you got your Ethernet driver back following the System Restore (since you were able to post here), you might try installing each of those three patches separately (install/reboot, install/reboot, install/reboot) so as to isolate the problem patch.
1 user thanked author for this post.
-
Thank you.
Will try it.
1 user thanked author for this post.
-
-
OK. Survived
Windows Malicious Software Removal Tool x64 – May 2019 (KB890830)
Now for the big one.
2019-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4499164)
One way or another, I’ll be offline until Saturday night. Will report then.
Wish me luck…..
1 user thanked author for this post.
-
Thanks. But I guess I needed more than luck.
When I installed
2019-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4499164)
I lost my Ethernet connection again. I had to roll back with System Restore.
1 user thanked author for this post.
-
Morty, glad to see you’re back, but sorry your lost your connection. You said, “I’m running Microsoft Windows 7 Professional, Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC. With Microsoft Security Essentials…”What is your CPU, Graphics and Network card manufacturer? Along with the OS, we like to know what NIC/drivers you have so others can be forewarned.
Thanks.
1 user thanked author for this post.
-
-
woooooooo, OK let’s see Morty.
Intel(R) Core(TM) i7-2600 CPU That is a good one I7.
Intel(R) HD Graphics OK that is good but what model. Driver Version 9.17.10.3517 nice.Go to Control Panel, System, Device Manager.
Under Display Driver it should say Intel with more info on its name/model.
Under Network Adapters what is the name(s) there?? There may be one for wireless and one for wired. If so which are you using?Thanks.
1 user thanked author for this post.
-
@Morty –
Different anonymous here than the one you’ve been dealing with.
Last year, many folks were having the exact problem you are with their networking cards after installing the monthly rollups for Windows 7…no network card functionality. So, Microsoft published some advice to help those folks out of their tight situation. I copied and pasted it last year in the event it happened to me, so here it is below, word for word in two separate “paragraphs”:
To locate the network device, launch devmgmt.msc (the Device Manager from Control panel as described in the other anonymous’ post just above this one); the network card may appear under Other Devices. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
a. Alternatively, install the drivers for the network device by right-clicking the device and choosing Update. Then choose “Search
automatically for updated driver software” or “Browse my computer for driver software”.The steps above are written from the viewpoint of having already installed the monthly rollup and having no network card functionality as a result, so you’ll have to install the rollup first.
For the first quoted paragraph above, I added some wording for clarity’s sake.
Either one of us can help you through re-enabling your networking card, so feel free to ask, especially if you feel you’ve gotten in over your head.
Another good idea would be to start a new thread to be able to fully troubleshoot this issue, as we’re getting off topic for this one.
1 user thanked author for this post.
-
Morty, anonymous 1686536 “6536” here, You have several helping you now.
anonymous 1692108 “2108” Thank you for that information. I had not made it that far, but remembered “this happened last year.” That is good data and since it happened to you you are familiar with it. My NICs didn’t have any issues last year.
1 user thanked author for this post.
-
-
-
Win7 32bit Group A with Avira free, i have installed the May rollup and the .Net rollup and have experienced no problems, although the May rollup was a very slow update.
1 user thanked author for this post.
I have done the updates as advised by Woody and crew on a Windows 7 Pro running ESet and Malwarebytes Pro. No adverse effects that I am aware.
1 user thanked author for this post.
Made the update of the monthly rollup for Windows 7 – KB4499164. (Waiting with the NET opdate). Did the monthly update tool for removal of malware first separately (KB890830).
All went well. There was a pretty long closing time (perhaps 5-10 minutes) after the installation. Next reboot went smoothly.
My troubles previously perhaps were related to the fact that being impatient I reset the machine before it had finished closing second time (there was no message “Don’t shut down the computer” as there was during installation). Anybody agrees with this? (Just to recapitulate the former troubles: the multiboot system (grub) was disturbed resulting in not being able to boot anything).
-
That sounds reasonable. You have to be patient with Windows (in more ways than one). Jump the gun and you just shoot yourself in the foot sometimes.
5 users thanked author for this post.
-
Hello JustAsking, your anonymous buddy from above. I must say I agree with PKCano. There do seem to be times that Windows is stumbling around with the hard drive light flashing wildly, yet no mention to wait. I, SueW and others will wait for a few minutes if needed for that drive light to settle down before we click restart. I always install one-by-one and reboot after each patch. After the last patch installs (you are finished), let the computer sit an hour and not go to sleep so the idle tasks, and .NET MscorsVW compiler can run or you might have an annoyingly sluggish computer.
Windows 7 Group B
Edited a section to prevent confusion.
1 user thanked author for this post.
-
-
-
There is a picture about 3-4 posts down from that link, with a BIG RED ARROW on it showing where it is in AKB2000003.
Here is a PICTURE from the MS Catalog;
1 user thanked author for this post.
-
-
-
Didn’t I just post my April feedback not too long ago?? 🙂 Here’s May’s:
1 – imaged my disk with Macrium Reflect
2 – downloaded Updates KB4499175 (May SO), pciclearstalecache, and KB4498206 (IE11 May Cumulative)
3 – installed the May SO and IE11 Updates and then rebooted; waited 15 minutes
4 – checked “Windows Update” => 5 Important (all checked): 2 Office 2010 and 3 Win 7; 1 Optional: unchecked
5 – unchecked and hid “Important” Update KB4499164 (May Rollup)
6 – hid the unchecked “Optional” Definition Update for Microsoft Security Essentials
7 – checked “Windows Update” again => 4 Important: 2 Office 2010 and 2 Win 7: all checked; 1 Optional: unchecked
8 – hid the unchecked “Optional” Definition Update for Microsoft Security Essentials (again)
9 – checked “Windows Update” again => 4 Important: 2 Office 2010 and 2 Win 7: all checked
10 – unhid 0 hidden updates to install
11 – installed 4 Updates: 2 Office 2010 (KB4464567 and KB4464524), .NET Framework (KB4499406), and MSRT (KB890830)
12 – rebooted and waited around 45 minutes
Notes: KB4499175 (May SO) was 100 mb (about twice as its usual size) and Windows Media Player needed to be reconfigured again.
Many thanks to Woody, PKCano and her enormous patience (!), and everyone else who continue to contribute their time and expertise, or who post their own results!
Win 7 SP1 Home Premium 64-bit; Office 2010; Group B (SaS); Former 'Tech Weenie'-
SueW, thank you for your post. They are always detailed and I feel people benefit from them. I am still holding off for a while and will post my update When the time comes.
Windows 7 Group B
1 user thanked author for this post.
-
I updated my Win 7 64-bit home system on Thursday 5/16, and my employer patched my Win 7 work computer 5/17.
If you’ve disabled the libraries feature you will need to restore default settings BEFORE installing the May patch. That was also the case for April.
1 user thanked author for this post.
-
The only thing I could suggest is to be sure you got the right bitedness. If you did not, it would say the update was not applicable.
1 user thanked author for this post.
-
BillC, that is an odd situation. Like PKC said could you had the wrong bit or maybe “embedded” version of update by mistake? I do have both the history and installed KB4486564 in my Windows 7.
I did see where a person at reddit with a 2008 server had a similar issue and part of his solution was to make sure he had the new version of Windows Update Agent. Are you up to date on your WU (windows update) and SSU (servicing stack update)?
KB4486564 still Shows As Required Long after Successful Installation
https://www.reddit.com/r/SCCM/comments/ay1pak/kb4486564_still_shows_as_required_long_after/
“specific to my lone 2008R2, it was a combination of an out of date WUA agent and just refreshing the state message”How to update the Windows Update Agent to the latest version
https://support.microsoft.com/en-us/help/949104/how-to-update-the-windows-update-agent-to-the-latest-versionKeep us posted.
1 user thanked author for this post.
-
For Anonymous and PKCano:
It was the correct version for Win7-64: 2019-02 Security Only Quality Update for Windows 7 for x64-based Systems (KB4486564) or exact file name of (windows6.1-kb4486564-x64_ad686ee44cfd554e461c55d1975d377b68af5eca.msu)
I just re-downloaded the February 2019 SO patch and compared the full file name, and the file size with my archived version and it is identical. I maintain an archive of every SO patch since the new patching system started. I will try to install again using the new version, but expect the same result. This is a new patching wrinkle for me.
I am using the most current Servicing Stack Update with the SHA-2 capability.
Update: Here is a screenshot of the exact notice that the attempted install gives:
-
Don’t keep messing with this one. It’s clearly a matter of supersedence. It cannot be applied after the April 2019 one. Also, disk cleanup removes it. This has happened before with the January 2017 Security-Only update.
Regards, VZ
2 users thanked author for this post.
-
-
-
First let me say, that I have become exhaustively tired of having to hold my breath every month for the last couple of years, when it’s time to monthly Windows 7 update. And constantly expecting an explosion of either epic proportions (the total loss of Windows due to a non-working system backup), which happened, or a BSOD, of course it happened. I think I have lost at least 5 years of my life with the MMWW (Monthly Microsoft Windows Worries). However, I still remain a proud Windows 7 Home Premium 64 bit SP 1 Intel Core i5 520UM Arrandale 32nm Group B owner & user.
Well, after reading hints and tips from the people in the know on this sight, like disabling the Remote Desktop & Remote Configuration, disabling the disk defragmenter, my antivirus is not one of the problem ones, though I made sure it was totally updated, and I am using the GWX Control Panel Monitor. I bit the bullet last night, and using SueW’s excellent how-to update list for May (thank you SueW! I really do look forward to your lists!), I downloaded Updates KB4499175, pciclearstalecache, and KB4498206, placed them in a folder created on desktop. I had a minor problem with the KB4499175 installation. It always takes only 3-4 minutes to install the SO update. Usually within seconds, the percentage of completion message pops up (from 7% to 30%) with the message, ‘Please don’t shut off computer’. There was no % message. Period. I waited 1/2 hour. The only message was ‘Configuring download… Please down shut off computer’. Finally after 30 minutes I did shut down computer, waited 15 minutes, turned it back on, and the same message appeared on the desktop, but the percentage crept up to 30%, as usual, the computer shut down, and the desktop appeared normally. Yeah!! I waited 1/2 hour, installed KB4498206 without incident, waited another 1/2 hour, then checked Windows update. I don’t have Office and don’t use Microsoft Security Essentials, so I hid that, and just installed NET Framework (KB4499406), rebooted and waited 1/2 hour. As of this moment, everything is working well.
Thanks again so much to SueW, Elly, Woody, PKCano, and so many others who have made this possible nightmare into just a bad dream.
-
-
I click on ‘Restart’ in the Windows Update box after installing the SO update, wait 15 minutes and then install IE update & again click on ‘Restart’ wait 15 minutes. In the past, I tried once installing them both, the SO then the IE Cumulative, and then clicking ‘Restart’, but it didn’t work (received error message). So for the last 6 months or so I install each Update separately, ‘Restarting’ in between. The only time I’ve ever completely shut down the computer during an installation was last night when there was no percentage processing message for the 1/2 hour. I pressed the shutdown button, waited another 1/2 hour then turned it on. It went to the desktop, and began showing the proper processing message. This afternoon, turning it on, everything seems to be working properly, except that I had to reconfigure my media player. No biggy!
Thank you again so much for showing concern. Both you and so many other people on ‘Ask woody’ are genuinely caring individuals.1 user thanked author for this post.
-
-
Morty, anonymous “6536” here. anonymous “2108” may have a solid solution, look into what he said. Below are some items I found. One is about this happening last year and the fix MS had at that time.
I know getting online is most important, but if you wish to update your NIC drivers see below the comments of the previous patch event to the Intel and MS driver suggestions. Do what you feel best with.
This happened back in March/April of 2018. Below was the fix at that time.
NIC settings are replaced or static IP address settings are lost after you install KB4088875 or KB4088878
https://support.microsoft.com/en-us/help/4099950/nic-settings-are-replaced-or-static-ip-address-settings-are-lost-afterMr.Brian
https://www.askwoody.com/forums/topic/march-2018-patch-tuesday/#post-179462
Below that post Mr. Brian said, “This update doesn’t appear to replace any existing files. Rather, it runs a file it contains called PCIClearStaleCache.exe.”Drivers:
Intel Site:
https://downloadcenter.intel.com/product/47549/Intel-82579-Gigabit-Ethernet-Controller
Intel Network Adapter Driver for Windows 7 Version: 23.5.2 (Latest) Date: 2/6/2019, 54.44 MBWindows Catalog: (this is what you probably have an MS driver being version 12…)
Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection (64bit)
Windows 7,Windows Server 2008 R2, 11/12/2015 12.15.31.0 608 KB
https://www.catalog.update.microsoft.com/Search.aspx?q=82579LM1 user thanked author for this post.
-
What you need is the Window Media Creation Tool. Google it and download it from Microsoft.
1 user thanked author for this post.
-
-
-
-
-
-
The one to be released later this month is 1903. You can wait for it until any time before Nov. 2019 – that is when 1803 will be EOL.
The thing you shouldn’t do is upgrade to a new version immediately after it is released, because it will be full of bugs. I would give 1903 AT LEAST three months (depending on reports) after release to even consider upgrading to it.
1 user thanked author for this post.
-
-
Don’t “Check for Updates” and you should be OK.
1 user thanked author for this post.
-
-
-
-
A Thread or Topic is started the same way you started THIS ONE.
Waddayaknow?! I don’t even remember doing that.
Well, before I start a new thread, let me see if I can figure out what to do with what I’ve been told.
Thanks again.
1 user thanked author for this post.
-
Hi @morty, if you’re game to try installing that problematic rollup again, here’s something you might try: before installing the rollup, find the name of the Ethernet driver that you’re losing when the rollup gets installed and copy it to a different, safe folder.
To do this, go into Device Manager and find your Ethernet driver. Right-click on it and then click on Properties at the bottom of the context menu. Then go to the Details tab and click on the little arrow that’s at the right end of the button just below where it says “Property.”
Now scroll down the menu that will drop down, and look for “Inf name”. Once you find it, select it with the mouse and the field named “Value” will show you the name of the relevant file.
Now go to your Windows directory in Windows Explorer and do a search for the file with that name. (It’s probably in the C:\Windows\inf folder.) Right-click on the search result for that .INF file and select “Open file location.” Now you can copy the file to a different folder–say, the Documents folder; the idea is to place it somewhere you’ll remember. Make sure to copy it and not to move it to that other folder. Also make sure to write down the folder where Search found the file, so that you can put it back there later if necessary.
Now install the problematic rollup (before this, make sure that System Restore is still turned on). Reboot when requested.
If, after rebooting back into Windows, you find that you’ve lost your Ethernet connection once again, go back into Device Manager and “update” the driver, although in this case it’s simply bringing back what you already had. When it asks where to find the driver, type in the folder where you stored the copy of the .INF file.
I know this method works because I did it just three days ago on a Vista machine that I was putting into service. (Don’t ask… 🙂 ) After a certain round of patches to bring the OS more up to date, the machine lost its Ethernet driver and I had to do a System Restore to get it back, then I carried out precisely the same procedure that I described above.
If this doesn’t work for you, you can use System Restore to put things back they way they were before the rollup and you’ll be no worse off than you were before.
Give a holler if you get stuck at any of these steps. I thought about adding screenshots, but this post is already quite long.
1 user thanked author for this post.
-
Hi Morty 6536 here, Yes Microsoft will or should eventually get the problem fixed. The last time this happened they came out with the below about 3 weeks later.
NIC settings are replaced or static IP address settings are lost after you install KB4088875 or KB4088878
https://support.microsoft.com/en-us/help/4099950/nic-settings-are-replaced-or-static-ip-address-settings-are-lost-afterKeep your eyes on Microsoft patches.
Another idea that goes against PKcanos advice, is to run the PCIClearStaleCache.exe file like Jamesbond did. https://www.askwoody.com/forums/topic/ms-defcon-3-get-windows-xp-win7-and-associated-servers-patched/#post-1647847 If it works then great, if not then restore and look at Cybertooth’s plan.
Cybertooth has a good way to fix it if you want to follow him. He is a good guy. He, I and others worked on a problem he had last November/December, in the “windows-7-pc-gets-very-sluggish” forum here.
Keep us posted Morty.
2 users thanked author for this post.
Now scroll down the menu that will drop down, and look for “Inf name”. Once you find it, select it with the mouse and the field named “Value” will show you the name of the relevant file. Now go to your Windows directory in Windows Explorer and do a search for the file with that name. (It’s probably in the C:\Windows\inf folder.) Right-click on the search result for that .INF file and select “Open file location.”
They headed me off at the pass. I found the file name but, lo and behold, search tells me there’s no such file as oem11.inf.
I’m going back to a typewriter…..
2 users thanked author for this post.
-
This is weird, but I had the same non-result when I looked up the Ethernet driver on my Windows 7 PC just now. Over the years, I’ve found that Windows Search isn’t the most reliable feature of Windows. In this case I had to go into the C:\Windows\inf folder myself to find it there.
Try repeating the search from within that folder, and if that fails, then scroll slowly up and down the contents of the folder (as I had to) until you find that oem11.inf file.
Another, almost equally tedious, way to do it would be to tell Explorer to search for all .INF files by typing *.inf in the search bar. You’ll get a ton of results, but that worked for me too.
1 user thanked author for this post.
-
Thanks. I checked the folder and it jumps from oem10.inf to oem14.inf (see screenshot). I also searched with WizFile and it drew a blank too.
Curiouser and curiouser.
1 user thanked author for this post.
-
That IS strange. Is the PC where you can’t find the Ethernet driver, the same PC where you’re posting to Woody’s from? If so, it would mean that you have a working Ethernet driver (since you can get on the ‘Net) but Device Manager is giving you the wrong information.
One way around this would be to visit your PC manufacturer’s website, find their page for your model, and download their Ethernet driver to a safe place, then proceed to install the rollup.
1 user thanked author for this post.
-
-
-
Hi Morty 6536 here, CyberTooth is right, I looked on my Win 7 and did have the OEM11.inf file in C:\windows\inf folder, so that is weird.
I posted before 2 places to get the driver, and as CyberTooth said, if you have a Dell (you said previously – BIOS Version/Date Dell Inc. A11, Fri 12/30/11) you should be able to go to DELL and with your “tag number” or model find the drivers for that PC. Dell is usually VERY easy to find drivers.
Drivers:
Intel Site:
https://downloadcenter.intel.com/product/47549/Intel-82579-Gigabit-Ethernet-Controller
Intel Network Adapter Driver for Windows 7 Version: 23.5.2 (Latest) Date: 2/6/2019, 54.44 MBWindows Catalog: (this is what you probably have an MS driver being version 12…)
Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection (64bit)
Windows 7,Windows Server 2008 R2, 11/12/2015 12.15.31.0 608 KB
https://www.catalog.update.microsoft.com/Search.aspx?q=82579LMDon’t give up yet Morty.
2 users thanked author for this post.
Cybertooth, <
-
