|
MS-DEFCON 2:
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it.
|
-
August 2019 Security patches: It’s a biiiiiiiiig month
Posted on Comment on the AskWoody Lounge- This topic has 197 replies, 43 voices, and was last updated 1 year, 4 months ago.
Viewing 57 reply threads-
-
Looks like we’re getting 90 separate patches for 93 individually reported security holes (CVEs).
[See the full post at: August 2019 Security patches: It’s a biiiiiiiiig month] -
The 2019-08 Security-only Update and IE11 Cumulative Update have been added to AKB2000003 for Group B patchers (and anyone else who needs them).
NOTE: The links in AKB2000003 are direct download links to the MS Update Catalog.
A reminder for those still on Windows 7 and/or Server 2008: SHA-2 Code Signing has become mandatory. You will also need to download KB4474419 (the SHA-2 v.2 update dated 8/12) and the Servicing Stack KB4490628 if it has not been previously installed.
Also be sure you have installed the Servicing Stack Update for Win 8.1 KB4504418
UPDATE: See #1907649 below UPDATE UPDATE
No, SO KB4512486 is telemetry-free
-
The MS pages for KB4474419 say the following:
-
This security update was released March 12, 2019 for Windows 7 SP1 and Windows Server 2008 R2 SP1.
-
This security update was updated May 14, 2019 to add support for Windows Server 2008 SP2.
-
This security update was updated June 11, 2019 for Windows Server 2008 SP2 to correct an issue with the SHA-2 support for MSI files.
-
This security update was updated August 13, 2019 to include the bootmgfw.efi file to avoid startup failures on IA64 versions Windows 7 SP1 and Windows Server 2008 R2 SP1.
If the latter point applies to your situation, you will definitely need to apply this patch.
UPDATE: MS pages also say:This update also includes the following improvements:
-
Further hardening of infrastructure files that are used by the Windows Update and Microsoft Update client.
-
A more secure communication channel between the service and the Windows Update and Microsoft Update client has been added.
So it would seem this patch should be installed for Win7 in general, not just IA46 based systems.
-
-
-
From my simplistic understanding, most Windows users are on x64 (64-bit) or x86 (32-bit) architecture. The IA64 architecture is different, mainly meant for servers, and usually cannot run 32-bit applications (unlike x64 which usually can). Most of us running a desktop or laptop don’t have IA64.
-
-
-
-
August Beta Test Report Windows 7 x64 Updates
Important
– Windows Malicious Software Removal Tool x64 – August 2019 (KB890830)
– August 2019 Security Monthly Quality Rollup Windows7 for x64 (KB4512506)
– August 2019 Security Update for Windows 7 for x64 (KB4474419)Optional
– Microsoft .NET Framework 4.8 for Windows 7 x64 (KB4503548)Selected the important updates.
– KB4512506 failed.
– KB890830 installed.
– KB4503548 installed.I rebooted and checked for updates.
Selected important and optional update.
– KB4512506 installed.
– KB4503548 installed.I rebooted. The system came up. The system automatically rebooted again.
Total time to install four updates was about 45 minutes with an initially failed update and a very slow download time.
The guinea pig did not die and the system functions. However, this was a cumbersome update process.
BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr-
Addendum and correction:
First pass, selected the important updates.
– KB4512506 failed.
– KB890830 installed.
-KB4474419 installed, not KB4503548.BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr
-
-
-
(WU) SMQR patches certainly will but, as for Security Only patches we need reports in to confirm.
Problems controlling W!N10 updates:
https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/1 user thanked author for this post.
-
-
-
I disabled the two telemetry things in Task Manager which were installed by the July SO update. After installing the August SO update, these two tasks remained disabled. The July SO update telemetry items in Task Manager are set to run infrequently. This suggests that these two tasks merely gather basic information about the computer, as in what updates and programs are installed. In other words, no “real time” data is constantly gathered, unlike when KB2952664 is installed.
A half rant, yet food for thought…
The upshot is that I think that users should install the July SO update and then simply disable the two tasks in Task Manager which gather some limited telemetry. I theorize that Microsoft simply wants to know why so many users refuse to upgrade to Windows 10. Is it because Windows 7 users are using older programs which will not run under Windows 10? Is is because many Windows 7 users are using much older hardware which may have issues with Windows 10? Is it because many Windows 7 users refuse to accept the telemetry which comes with Windows 10? Perhaps these are things which Microsoft wants to know.
On the other hand, and after the abysmal failure of Windows 8, Microsoft could have simply asked their consumers these very questions via online surveys. Microsoft has a penchant for belatedly realizing that they royally messed up in anticipating what consumers really wanted. It seems that it takes Microsoft at least a solid three years to begin to acknowledge that they didn’t get it right.
For the first time in Microsoft’s history, the Microsoft Windows branch (under Sinofsky and subsequently under Nadella), achieved the infamous milestone of releasing two OS versions in a row which were not well received. I wish that Balmer had been brought back to once again perform his magic and fix Windows 8, long before we ever got to this thing which is called Windows 10. The only company which I can think of which was equally inept is Chrysler.
Everyone, please do not respond to my half rant, since doing so would take this topic way off topic. If you want to respond, create your own rant in the appropriate rant section of the forum.
-
+1 for installing July SO
i think you mean Task Scheduler not Task Manager 🙂
1 user thanked author for this post.
-
I checked my Event Viewer logs. I too have the InvProv message with Event ID 63 which showed up after installing KB4507456. I did a bit of googling, and I see that installing KB2952664 also causes the same message in Event Viewer. Some versions of Office also cause the same message. I do not see signs that the July SO installed any deep telemetry like KB2952664 did.
1 user thanked author for this post.
-
-
-
I cannot say for sure
the OS will still works perfectly with August SO KB4512486 (which require SHA2 KB4474419)
but it will be missing some of security fixes for July vulnerabilities
1 user thanked author for this post.
-
-
-
-
-
I am not being offered the Win 7 monthly rollup KB4512506 (I still see the 2019-07 Preview KB4507437).
I am assuming that this is due to the following:
Symptom:
Microsoft and Symantec have identified an issue that occurs when a device is running any Symantec or Norton antivirus program and installs updates for Windows that are signed with SHA-2 certificates only. The Windows updates are blocked or deleted by the antivirus program during installation, which may then cause Windows to stop working or fail to start.Workaround:
Microsoft has temporarily placed a safeguard hold on devices with an affected version of Symantec Antivirus or Norton Antivirus installed to prevent them from receiving this type of Windows update until a solution is available. We recommend that you do not manually install affected updates until a solution is available.I have Norton Security 22.18.0.213 installed on my Win 7 system.
Assume that there will be many others in the same situation.
-
-
-
Symantec bought Norton in 1990.
Few people realize that Norton, prior to Symantec, was a PC utility company WITHOUT an antivirus product. Norton Antivirus is just a convenient use of a trusted name.
AFAIK, Peter’s still living on Martha’s Vineyard. He’s no longer on the board of Symantec. Rarely hear about him these days, except for his philanthropy.
-
Broadcom bought the Enterprise Security products from Symantec a few days ago, making them once again owned separately from the Norton (home/personal) line. (The transaction will likely close before year-end.)
Broadcom intends to keep the Symantec nameplate in place for now.
1 user thanked author for this post.
-
Thanks @woody – that’s good to know about Symantec and Norton. I guess the Norton name still carries some cachet if people still use it.
-
-
-
-
I’m seeing the same thing as ? above with my Norton Security on Windows Pro SP1 x64.
Windows Update is now showing me 2019-08 KB4474419 (again) and the MSRT, but not KB4512506 (the real August Security Update).
Windows 10 Pro x64 v1909 and Windows 7 Pro SP1 x64 (RIP) -
There is not urgency/need to install any of the August updates at this time. We are on DEFCON 2. WAIT!!
There is a conflict with Semantec/Norton EndPoint Protection and the updates signed with SHA-2 only. This affects both the Monthly Rollup and the Security-only Update. Until this is worked out, MS has a block in Windows Update on computers running this security software, so you will not see (and should not install manually) the August SQMR or SO.
-
-
-
-
Windows 7 x64 Home Premium Group A, McAfee AV
I installed the SHA-2 update KB4474419 back in March. It appears that the August update to KB4474419 only applies to IA64 and not X64 based systems. Therefore, I am assuming that I will not need to reinstall this update.
What is unclear is whether I will even be offered this update. I would imagine that WU would only offer KB4474419 as an “exclusive” update. Therefore, if I am not offered the update, should I use the technique of hiding all of the other updates to see if KB4474419 appears as an “exclusive” update? Or is it preferable not to attempt to reinstall the update (even if replacing the March update version with the August update version does no harm) as the August update only applies to IA64 based systems according to the documentation?
-
KB4474419 is not an exclusive update.
Edit: If you are not offered the patch through Windows Update, I would recommend waiting to download and manually install it.
1 user thanked author for this post.
-
Hi PKCano,
I am not doubting your claim that KB4474419 is NOT exclusive; however, the documentation for KB4474419 indicates that installation of this update requires a reboot. Wouldn’t that mean that one should install this update by itself and then reboot before attempting to install any other offered updates? I would imagine that installing KB4474419 along with the August monthly rollup concurrently would cause the rollup installation to fail, even when KB4474419 is installed first by WU before attempting the installation of the August monthly rollup.
Perhaps this explains why the user Geekdom reported that the installation of the August monthly rollup KB4512506 failed to install on its first attempt, as that user indicated that KB4474419 was included in the set of updates that were received from WU.
As an aside, is there a convenient way to check whether an update is marked as exclusive?
-
KB4474419 is NOT exclusive. Many Win7 updates “require a reboot.”
I just installed, on my Win7 SP2, KB4512506 Rollup, KB4474419 SHA-2 v2, and KB890830 MSRT at the same time through Windows Update with no problems, no failures, no second reboot, no error messages.
-
Selected the important updates. – KB4512506 failed. – KB890830 installed. – KB4503548 installed.
KBKB4012215 is the installer for .NET 4.8 on Win7. It is not an update for the operating system. If I had to guess, I would suspect this for causing @geekdom ‘s problem. Just saying…
1 user thanked author for this post.
-
Reiterating:
First pass, selected the important updates.
– KB4512506 failed.
– KB890830 installed.
-KB4474419 installed.Optional
Second pass, selected important update that failed and optional update.
– KB4512506 installed.
– KB4503548 installed.There is an error in my beta test report. Could someone correct it?
BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr -
Selected the important updates. – KB4512506 failed. – KB890830 installed. – KB4503548 installed. I rebooted and checked for updates.
KB4503548 is the installer for .NET 4.8
See #1907520.1 user thanked author for this post.
-
Hi PKCano,
I had meant to say that KB4474419 is listed as a prerequisite to installing the August rollup KB4512506. That fact along with its required reboot caused me to inquire whether I should install KB4474419 separately prior to the installation of the August rollup. Anyway, that’s what I did and it seems to have worked. Thanks!
1 user thanked author for this post.
-
Yes, install KB4474419 by itself and then reboot before installing any other updates.
2 users thanked author for this post.
-
-
-
-
-
-
But the Symantec support article says[Verbatim]:
“Windows 7/Windows 2008 R2 updates that are only SHA-2 signed are not available with Symantec Endpoint Protection installed”
And it’s the Press that’s Adding that Norton Branding so maybe that AKA needs to be clarified with Symantec. I’m running an ISP provided version of Norton Security Suite and there that Norton branding is on the product but in the quoted statement above on the Branding that is only “Symantec Endpoint Protection” so I assume that Symantec’s branding is correct. But clarification is certainly needed with the Press asking Symantec if that actually includes any products with that Norton name included in the product’s branding.
1 user thanked author for this post.
-
-
-
-
This kind of looks weird and out of place for Windows update KB4512508. Extract from: https://www.ghacks.net/2019/08/13/microsoft-windows-security-updates-august-2019-overview/
Fixed the MIT Kerberos realms issue that prevented devices from starting up or caused them to continue restarting.
Security updates to Windows App Platform and Frameworks, Windows Storage and Filesystems, Microsoft Scripting Engine, Windows Input and Composition, Windows Wireless Networking, Windows Cryptography, Windows Datacenter Networking, Windows Virtualization, Windows Storage and Filesystems, the Microsoft JET Database Engine, Windows Linux, Windows Kernel, Windows Server, Windows MSXML, Internet Explorer, and Microsoft Edge.my bolding never thought I’d see the day TBH
Problems controlling W!N10 updates:
https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/ -
-
-
-
-
-
saw this post near the end of August:
https://blogs.windows.com/msedgedev/2019/08/30/update-removing-flash-microsoft-edge-internet-explorer/seems like MS plans to discontinue and eventually remove Flash for MS Edge & IE
1 user thanked author for this post.
-
-
-
-
It’s a small thing, but it’s worth mentioning that the availability of .NET Framework 4.8 to versions of Windows prior to 1903 is going to be throttled over the coming weeks and months. Doing a “Check for Updates” will bypass the throttling, but otherwise it’s not going to show up right away for many people.
.NET 4.8 is already included with Windows 10 1903 so none of this applies there.
BTW, the main reason to install .NET 4.8 is that it improves startup time on a lot of .NET applications, in some cases by more than 20%.
-
Windows 8.1 Pro x64 on HP Laptop
Installed SMQR KB4512488 via WU
System rebooted, allowed 10-15 mins to cease SSD activity.Scrutinised the following for any changes prior to re-connecting online:
Event Viewer
Task Scheduler
Performance Monitor/ Data Collector Sets/ Event Trace Sessions
Performance Monitor/ Data Collector Sets/ Startup Event Trace Sessions
GP settingsResults = no changes
Configuration Notes:
Diagtrack removed early 2018 and hasn’t returned.
MRT disabled from downloading.
uPNP disabled
Windows Defender Antivirus Security Intelligence Update 1.299.1918.0SFC /verifyonly displayed:
WU review of update history
So far so good on win8.1 🙂
EDIT: Also updated a Haswell Desktop and Ivybridge Laptop again no issues with either. device.
Problems controlling W!N10 updates:
https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/ -
Windows 7 Group B computers. I am now fully patched through August. Note that there is a bug in the Windows Update manual installer. Once updates are installed and if you click the Restart button in the Windows Update window, your computer might hang when shutting down and while trying to close the Windows Update program. I first noticed this bug starting last month, and the results are bogus errors being recorded in Event Viewer. The errors state that the Windows Update(s) were not successfully installed, when in fact they were.
So until MS gets this bug fixed…
If you want to reboot after installing one or more Windows 7 updates, click Cancel when you are asked to reboot your computer. Doing so causes the Windows Update manual installer to close. Then reboot your computer by going to Start and then Restart. You might want to use this procedure for the time being, even when installing updates via Windows Update.
-
-
Windows 7 Home Premium x64, Avast AV
First installed:
– KB890830
– KB4512506
– KB4474419System rebooted twice.
Then I installed KB4503548 and after that reboot I got the NET Language Pack offered, so I installed that one as well.
No problems and no telemetry re-enabled.
-
-
-
-
How’s that is an upgrade move? it’s actually a discouraging move (i.e. we are securing Windows Update)
by the way, the v2 release for x64 and x86 does not have any new files or changed ones, only the digital signature security categories are updated
-
-
WARNING!!!
looks like updates KB4512486 AND KB4512506 kills Windows 7 with nvme SSD drives. two out of ~100 pc’s won’t boot with these updates installed, and only these two has nvme SSD as boot drives.
tried to remove both and install separately – it’s enough one of these patches to kill Windows 7 machine.
2 users thanked author for this post.
-
-
-
-
Boss, just so I’m clear, do we need to install KB4517297 from Microsoft Catalog before attempting to install KB4512506?
I am on WIN7x64 with latest versions of KB4474419 and KB4490628 already installed.
In either case, I’m holding off installing KB4512506 and KB4503548 as per current DEFCON-2. Thank you for all the support and expert advice you give people on askwoody.com
1 user thanked author for this post.
-
Boss, just so I’m clear, do we need to install KB4517297 from Microsoft Catalog before attempting to install KB4512506?
When you install KB4512506 it will break VB6, VBA and VBScript. If none of your programs are affected, you can stop there, b/c the fix will be in the Sept. Rollup. If you ARE affected, you can EITHER install KB4517297 (which is basically an SO with the fix) OR the 2019-08 Preview Rollup. I would recommend the former.
I’m holding off installing KB4512506 and KB4503548 as per current DEFCON-2
Good for you for waiting. When the time comes, I would recommend hiding KB4503548 (the installed for .NET 4.8 on Win7) for a while. If none of your programs require the latest version of .NET, it can wait for a while (several months, even).
Remember: We’re still on DEFCON 2
-
-
-
-
I have one machine too that got BSOD 0x0000007B INACCESSIBLE_BOOT_DEVICE after installing KB4512506, it uses a Samsung 960 EVO NVMe SSD.
I tried to use the latest Samsung NVMe driver instead of the Microsoft one bundled in KB2990941 but it did not help.
The fix described in KB2839011 for uninstalling a patch from the WinPE environment did work fine, as did restoring a previous recovery point.
What is strange is I have another workstation with a Samsung SM961 NVMe SSD that I held off to update until today when I could do a full backup but it went through without any issues!
I have realized the problem is not with NVMe SSD drives, it is with UEFI boot mode, which is a requirement for NVMe but can be used with any other drive as well.
Now I know why the second machine accepted the patch without issues: it had the “Win7 post SP1 rollup” patch KB3125574 applied.
Contained in this rollup is the recommended update KB3133977 for Bitlocker.
That patch is what works as a workaround for the problem: if you have it installed the system can then accept this months patch Tuesday patches: KB4512486 or KB4512506.
Microsoft has updated the patch notes for the latter with that info too, however they have done nothing to stop PC’s being bricked by the update still, as KB3133977 is still only listed as a recommended update!1 user thanked author for this post.
-
-
-
From Norton Community Forum:
Re: Is it safe to install August 2019 Windows 7 update??
Posted: 13-Aug-2019 | 3:56PM • Edited: 13-Aug-2019 | 3:59PM • PermalinkI’m running Norton Security v. 22.18.0.213 on Win 7 SP-1 Pro x64.
Windows Update informed me that KB4474419 was available. I installed it, and my computer works fine.
This update, however, is not the problem. The problem is apparently with KB4512506 — Monthly Rollup and KB4512486 — Security-only update. Even after installing KB4474419, MS Updates didn’t offer me either or the problematic ones.
The Symantic Enterprise KB article only indicates that the problem is with Enterprise Endpoint Solutions; it doesn’t mention any of the Norton products at all.
The answers provided to this Forum Thread are not at all clear except for this: “Defer the update until Norton has an official statement AND it clearly states a patch is available BEFORE attempting to install those updates at a later time.”
This should be in big red letters at the at the head of this Forum. I’m sure lots of Norton users around the world are wondering what’s going on with the August MS updates.
I’m wondering out loud how Norton intends to distribute its official statement and clearly state that a patch is available to address this specific issue.
And
As outlined in 2019 SHA-2 Code Signing Support requirement for Windows and WSUS, Microsoft will release an update to Windows 7 SP1 on August 13th, where the Microsoft Windows Updates are now SHA-2 signed instead of SHA-1 signed.
We have identified the potential for a negative interaction between Norton and the changes explained within the Microsoft KB. Symantec and Microsoft worked together to only allow the update to be visible to versions of Norton that offer full support for Windows 7 Updates that are solely SHA-2 signed.
We will release a Norton patch in the coming days to support the installation of updates that are only SHA-2 signed.
We don’t expect much impact. We can recommend that the customers click on ‘Always Allow’ when there is an alert, thereby allowing the Microsoft applications to function seamlessly.
We will be posting about this issue on the public forums, if we see large impact.
We already have an Enterprise KB article for this issue.Norton Forums Global Community Administrator | Symantec Corporation
EDIT to remove HTML. Please use the “Text” tab in the entry box when you copy/paste.
Windows 10 Pro x64 v1909 and Windows 7 Pro SP1 x64 (RIP)1 user thanked author for this post.
-
CTF vulnerability (CVE-2019-1162) is scary.
What is vulnerable? Oh, just everything that contains text.
http://www.zdnet.com/article/vulnerability-in-microsoft-ctf-protocol-goes-back-to-windows-xp/-
? says:
hi, carpintero i’m hoping to have one of the on-site scholars look at this. i read the project zero page on it and it seems fairly important:
https://googleprojectzero.blogspot.com/2019/08/down-rabbit-hole.html
from the demos it looks like it only takes seconds to obtain system control but hey, i’m no computer scientist!
1 user thanked author for this post.
-
-
This isn’t “fake news” (quite), since the CVE-2019-1181 & CVE-2019-1182 vulnerabilities have been documented. Yet I haven’t see such an over-the-top media reaction since before Y2K. From CNN: https://www.cnn.com/2019/08/14/tech/windows-10-microsoft-security-update-trnd/index.html
Notice the headline: Microsoft urges Windows 10 users to update immediately
As Simon Pope said in the M$ blog post, there are a lot more Windows OS’s affected than just Win10. CNN states in the 1st paragraph: ‘Microsoft is warning Windows 10 users to update their operating system immediately because of two “critical” vulnerabilities.’ Again, it’s not just Win10. Here’s a CNN quote that is definitely #FakeNews:
‘There are “potentially hundreds of millions of vulnerable computers,” Simon Pope, Microsoft’s director of Incident Response, wrote in a blog post Tuesday.’ Search the blog post & you will NOT find the words “potentially hundreds of millions” blah, blah, etc. Sounds like one of CNN’s political reporters is moonlighting in the Business section… or it’s someone reminiscing about the Y2K panic. This final quote is not quite true:
“Other operating systems, such as Windows XP, are not affected.” WinXP isn’t, but see above, as well as the blog post. Could M$ have paid someone at CNN to start a panic among Win10 users & click “Check for updates”? Or was the Business reporter just bored?!
2 Machines for Now!
#1: Windows 8.1, 64-bit, back in Group A.
#2: Getting close to buying a refurbished Windows 10 64-bit, recently updated to v1909. 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...1 user thanked author for this post.
-
Gordon on Forbes is notoriously over the top. As you say there is a kernel of truth and then the rest is OMG the sky is falling the sky is falling!!!!!
Just like before you have to have RDP open and listening and most of us
- do not have it turned on or
- do not have it open directly to the web
Susan Bradley Patch Lady
-
someone reminiscing about the Y2K panic
What Y2K panic ? I worked for 2 months, many times for 36 hours with no sleep, updating banking software for Y2K, which was a real threat to our banking systems and clients.
Y2K was real.1 user thanked author for this post.
-
-
Well, I got burned – my 2008R2 primary domain controller would not boot after the updates yesterday. The other two 2008R2 servers here were not harmed by the updates. Our BDC is actually running 2008 standard, and it survived the updates unscathed (Well at least, it was able to boot afterwards…)
Shout-out to Veaam for saving my bacon once again ( rolled the PDC back to Sunday’s image)… now have to figure out ‘which patch was the killer..”
1 user thanked author for this post.
-
-
The “crash-and-burn’ auto update was installing these three…
the MS ‘security intelligence’ ( AV definitions)
the 4512506 quality rollup
the 4474419 security patch
( in that order)
After restoring from image backup, I tried installing the AV defs – they went in fine. Then I tried installing just 4474419 BY ITSELF. And that has rebooted OK!!
Right now I am downloading the 4512506, with crossed fingers…
The server in question is a bone-stock 2008 R2 Standard, fully updated with all non-optional updates (to date!) just running DNS and DC role, and nothing else. We have a gateway appliance that provides DHCP…
PS: differences from our other 2008 R2 servers :
its a physical machine ( the others are Hyper-V VMs) – and it’s running the DC role ( the others are file server and DB servers, respectively… )
-
-
No symantec anything on our 2008R2 DC . Furthermore…
Just confirmed : KB4512506 IS THE KILLAH! Fails the reboot, after applying that patch.
This after the KB4474419 was successfully applied, and successfully rebooted.
Interestingly (or not) as it was “applying”, it got to 30% and then appeared to abruptly jump to the reboot stage (and subsequently failed).
ROLLING BACK to the previous backup… disabling the updates till they get this fixed
-
Yet was anything Symantec ever installed? I ask because some low level drivers might have been left behind when uninstalling any free trials which came with the computer. Long story, yet I believe that some AV manufacturers deliberately leave low level drivers behind in order to mess with the proper functionality of subsequently installed competing AV products. To get rid of any such remaining low level drivers, one has run download and run the AV manufacturer’s full removal tool.
1 user thanked author for this post.
-
-
I had an issue with a couple of 2008R2 Vm’s today failing when trying to install KB4512506, other patches installed fine.
Bit more digging and I noticed on the problem VM’s that KB4490628 (March Servicing stack update) was not installed on them. Installed that and tried installing KB4512506 again, installed fine, rebooted with no issues.
Don’t know if the above might help?
1 user thanked author for this post.
-
-
-
-
-
-
-
? says:
thank you ek for the explanation! so this “new,” Window’s vulnerability can be described as just another one of many “potential” attack avenues not (currently) being exploited? and the real and present danger is using Window’s updates or Windows at all?
1 user thanked author for this post.
-
-
-
-
Hi everyone,
Thanks for all the great feedback and advice over time. A priceless resource!!
I usually wait to install monthly security updates (and usually under Group B), but given the reported critical issues with the August update and recent issues I’ve had with security-only updates, I went ahead with the full roll-up.
As others mentioned, there seemed to be an issue with the installation and configuration. In contrast to what I usually do when an install “gets stuck” (shut down, reboot, uninstall, and try re-installing), I let this one go ahead without my intervention. After three automatic reboots (which made be nervous, for sure!) and configurations (the first two were stuck at 15% and 30% completed), the update and configuration finally went through smoothly.
It’s probably not how this update is supposed to run, but I thought I’d toss out my experience.
I also installed KB4474419 (which looks like a retread from March(?)) that consistently previously failed to install, and the .NET Framework update (KB4507240) before attempting the monthly (August) security update.
My system is Windows 7, 64-bit. Just a regular person 🙂
I will add to others’ frustration in having to go through this muckity-muck every month (and often more frequently) with MS–argh!!
Emily
1 user thanked author for this post.
-
hi woody.
check out these recent blogs from Born’s Tech & Windows World site:
https://borncity.com/win/2019/08/14/symantec-norton-blocks-windows-updates-sha-2/
noted about the problems with the Aug. 2019 Win7 updates and Symantec/Norton
https://borncity.com/win/2019/08/14/windows-updates-kb4512506-kb4512486-drops-error-0x80092004/
yup. either KB4512506 or KB4512486 fails to install or complete because the KB4490628 update was missing or not installed. really best for Win7 users to sit back and wait, which is what I’m currently doing; I won’t patch any of the few Win7 machines I have until things get sorted out for several days (but I have already installed both KB4474419 and KB4490628 updates way back in March 2019)
-
The updates really aren’t playing nice this time.
Just wait to patch.
BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr
-
-
-
You should approve both.
The August KB4474419 v2 has changes from the March version.
But the MS pages for the August version say it does not replace the March version:Update replacement information
This update doesn’t replace a previously released update.
5 users thanked author for this post.
-
-
-
-
In my case, the March 2019 servicing stack was already installed 🙁
This has been a real anomaly… I fell into the trap of complacency (always installing the ‘security patches’) since Windows updates have been mostly harmless for the last year or so. And I have only wasted all this time troubleshooting because the patch is marked “security” and these was all this hype about this latest critical vulnerability.
NINE HOURS of after-hours overtime wasted researching this issue and trying all the various patch application permutations, and I have restored our domain controller from its backup about five times now. To add insult to injury, the rather blasé word from ‘Microsoft Contingent Staff’ is that that so-called “security patch” can just be ignored until NEXT MONTH ( see https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3feaf46-f5e5-4e78-a1b8-888eada3d6d6/patch-tuesday-08132019-windows-update-killed-our-2008r2-pdc-will-not-boot?forum=winservergen )
-
I have installed August updates on these test machines:
+ 3 Win7 (one is 32-bit) KB4512596 SQMR, KB4474419 v2 SHA-2, and MSRT. (all had KB4474419 v1 SHA-2 and KB4490628 SSU previously installed)
+ 4 Win8.1 (one is 32-bit) KB4512488 SQMR and MSRT.I have used Windows Update on all, installing all patches at once. Have had no problems with any of them.
Notice: I am not installing KB4503548, the .NET 4.8 installer on any of my Win7/Win8.1 computers.
-
-
In the past (history speaks on the side of caution) the initial release of a .NET version on Win7 (in particular) and Win8.1 has been problematic. Reference the initial version of .NET 4.7 on Win7 as an example. So, just like DEFCON says, I wait. That is the main reason.
Better safe than Microsofed.And, I don’t really have any need for it since I am not running programs that use/need .NET 4.8
-
The newly published .NET 4.8 packages are actually refreshed with latest fixes (including security fixes from July)
for Win7, it’s handled via separate bundled patch KB4503575
for other systems, the MSU/CAB packages themselves are updated1 user thanked author for this post.
-
for Win8.1, .NET 4.8 for 8.1 is KB4486105
https://www.catalog.update.microsoft.com/Search.aspx?q=4486105
also updated w/ July 2019 security fixes1 user thanked author for this post.
-
-
-
I always let installers call for .Net updates if required,
otherwise I just ignore them as a rule of thumb via WU or the catalog.
Problems controlling W!N10 updates:
https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/1 user thanked author for this post.
-
-
-
? says:
thank you ek for the explanation! so this “new,” Window’s vulnerability can be described as just another one of many “potential” attack avenues not (currently) being exploited? and the real and present danger is using Window’s updates or Windows at all?
Short answer to your 1st sentence: yes. But this vulnerability is very different than the processor side channel vulnerabilities like Spectre – which are (generally) computationally expensive to leverage (ie: complex and relatively slow). CTF is easy & fast to exploit to gain admin privs.
On your 2nd sentence: Well, if I made a statement like that I would be half serious.
I’ve been using Linux the majority of the time for years now.
I still run Windows 7 on some systems, but in doing so I follow these practices:
- MS updates are now often as risky as malware. So, I recently stopped patching. Prior to that, I always kept the systems up to date.
- The systems are behind a secure router with inbound/outbound rules set.
- I periodically inspect system activity (process, disk, network, etc.).
- I use a commercial Antivirus app and also do manual Defender scans.
- I use a local DNS server/filter and DNS services (like Quad9 and OpenDNS) to block risky/unwanted hosts/domains.
- The Windows systems never access the internet and especially: I avoid running a web browser of any sort on them. But if I absolutely have to, I use Firefox with a number of security/privacy addons (eg: noscript, privacy badger, UBlock, containers, etc.).
- I never store any sort of important documents on a Windows system anymore.
- The systems are never “always on”. I boot them when I need to use Windows and shut them down when done.
- Software/application wise: the systems are “frozen”. I don’t & won’t install any new Windows software (other than, maaaaybe, updates).
- I disable a number of unneeded Windows services and block telemetry.
So, yes, that’s a lot compromises & hoops to jump through just so I can (occasionally) use a a handful of Windows based apps I’m reluctant to abandon. Not sure how much longer I’ll be willing to put up with it.
4 users thanked author for this post.
-
? says:
again, many thanks ek for taking the time to reply and even more thanks for Woody, PKCano, abbodi86, and all the rest of the crew here for allowing me to vent my windows frustrations here and burn up precious airtime. all i really wanted to do is to finish out my windows 7 days in peace and then spin down quietly in January, but i know all to well that “you can’t always get what you want…”
1 user thanked author for this post.
-
-
-
Microsoft had many mistakes in wsus superseded relationships. many times I found wrong superseded patches. these kind of errors can be found easily when you compare the client scan result from wsus and on line update.
I didn’t try to find patches which should be superseded but not. they are hard to find. KB4474419 is very important or I think I won’t notice the duplicate.
but normally windows on line update is correct when wsus is wrong. the KB4474419 duplicate both at wsus and windows on line update. it is very strange to me.
-
August 17, 2019—KB4512514 (Preview of Monthly Rollup)
https://support.microsoft.com/en-us/help/4512514/windows-7-update-kb4512514The above preview just showed in the Windows Update queue as an optional update.
BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr2 users thanked author for this post.
-
Here’s the Win8.1 version (also Optional):
2019-08 Preview of Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4512478)
https://support.microsoft.com/en-us/help/4512478/windows-8-1-update-kb4512478
2 Machines for Now!
#1: Windows 8.1, 64-bit, back in Group A.
#2: Getting close to buying a refurbished Windows 10 64-bit, recently updated to v1909. 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...1 user thanked author for this post.
-
-
Have several 64-bit Win 7 Pro machines that history shows successful installation of KB4512506 followed by KB4474419
Have at least 1 64-bit Win 7 Pro machine that was on automatic update, applying the 2 patches + KB890830, and upon reboot, not possible to boot -> Error 0xc000225 Black screen – unable to boot anything off hard drive (SATA SSD). Pulled the drive & ran chkdsk – everything OK. Unable to boot to HP recovery partition either.
Boots to HP recovery from USB, but unable to repair startup.
I had made a pure Microsoft Recovery CD -> bootable USB using Backup/Create System Restore Disk, and with this, I was able to UEFI boot the USB, and run startup repair successfully. Machine booted normally. Applied KB4474419/ reboot successfully. Then tried KB4512506, and again neutered the machine/ same Error 0xc0000225. But, again able to recover with pure MS Startup Repair (not the one in HP’s recovery image).
Seeing other reports of this from various sites
Windows Boot Manager Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. Choose your language settings, and then click "Next". 3. Click "Repair your computer". If you do not have this disc, contact your system administrator or computer manufacturer for assistance. Status: 0xc0000225 Info: The boot selection failed because a required device is inaccessible. ======= Startup Repair - Name: System boot log diagnosis Result: Completed successfully. Error code = 0x0 Boot manager generic failure 0xc0000225 Root cause found: Boot manager failed to find OS loader. Repair action: File repair Result: Failed. Error code = 0xa Repair action: Boot configuration data store repair Result: Failed. Error code = 0x490 Repair action: System Restore Result: Completed successfully. Error code = 0x0
2 users thanked author for this post.
-
On window 7 machines with black screen of death after KB4512506 or the security only version of the patch I found removing all drives except c drive (operating system) drive and then booting up worked find. Then add the removed drives back and all should be ok if its what I ran into.
For some reason its scrambling the drive letters (identifiers) of the drives. Booting up with just the single drive straightens it out.
No clue why but it worked.
Crowz
3 users thanked author for this post.
-
Concering boot error 0xc0000225 – it seems to me, that the SHA-2 thing is causing this error – Windows 7 can’t read the digital signature of files, after installing KB4512506.
So try to install the Bitlocker-Fix KB3133977, that also helps with Stop error 0xc0000428. I got confirmation from German readers that it helped.
But be careful an ASUS board, because this patch prevents a boot. The KB-article for KB3133977 contains more details.
Microsoft Windows Insider MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
-
Morning all and after reading the commentary I certainly appreciate seeing your responses / questions. And what a ha ha, after Woody mention at the beginning of August that it should be a quiet month. As I say many times to my users, IT never sleeps.
Myself, will not wait till the end of the month as usual, and plan to start 2012 / 2016 Server updates next weekend. Though we’ll see what bugs come up between now and then before i finalize my decision.
A metaphor I’m telling my users who happen to catch the media’s reporting the “sky is falling, apply August patches NOW”, is as follows:
“Bluekeep and its siblings are like the boogie man, not sure if they exist now, so we’ll wait till Microsoft gets things figured out and then we’ll patch before Bluekeep turns into Godzilla.”.
This is the PG version, I have a non-PG version for those that appreciate the spice.
Take care,
IT Manager Geek
2 users thanked author for this post.
-
-
I’ll be working on that later this week, as another of my monthly “Patch Status” articles for Computerworld.
Right now, everything’s in a state of flux. And then some.
4 users thanked author for this post.
-
-
-
The 2019 SHA-2 Code Signing Support requirement for Windows and WSUS article is updated with more info for Windows 7
while it’s not listed as prerequisite, but the FAQ section now suggest to include update KB3133977 for new installations of Windows 7
those who have failed installations for already running Windows 7 OS can try the suggestion, particulary the last one (i.e. install KB3133977, reboot, run bcdboot.exe)
-
Knowing what we do now about KB3133977 and Win7, would it be easier to install 3133977 before installing ANY other updates for August if we didn’t install 3133977 when it was first offered back in 2017 and hid it instead?
1 user thanked author for this post.
-
Yes, KB3133977 should (had) be installed anyway
all recommended non-security updates are useful and safe, except the telemetry ones
1 user thanked author for this post.
-
-
-
KB3125574 is a convenience Rollup meant for quick updaating from a clean install instead of having to install a lot of individual updates.
All you need at this point is the individual patch KB3133977 which was one of the updates contained in KB3125574.1 user thanked author for this post.
-
-
-
-
-
-
This optional update just appeared in the Windows Update queue:
Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB4512193)
https://support.microsoft.com/en-us/help/4512193/august-20-2019-kb4512193BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr1 user thanked author for this post.
-
Here’s the Win8.1 version that appeared in my Windows Update queue:
Preview of Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1, RT 8.1, and Windows Server 2012 R2 (KB4512195) https://support.microsoft.com/en-us/help/4512195/august-20-2019-kb4512195
Capt. Obvious passes on that this is a Preview, and Optional at that. Easy to skip…2 Machines for Now!
#1: Windows 8.1, 64-bit, back in Group A.
#2: Getting close to buying a refurbished Windows 10 64-bit, recently updated to v1909. 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...
-
-
Here’s a little (perhaps irrelevant) trivia…
I just noticed that the PDC that got killed with last week’s security update happens to have what looks like a Chinese (??) language pack installed along with itsDOTNET framework…
Coincidence?
1 user thanked author for this post.
-
-
no issues on 1903 with the Aug 2019 patches for you, zero2dash (not even encountering any VBA/VB6/VBScript problems?)
I’m skipping the KB4512508 update for 1903 – I won’t install that patch on my friend’s PC running Win10 pro v1903 and will wait for the next update coming near the end of August that should fix some of the issues found with KB4512508.
1 user thanked author for this post.
-
-
-
-
-
-
-
Two interesting Microsoft statistics would be:
– testing performed in-house on software modifications and patches.
– turnover rate of Microsoft employees assigned to software testing.BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr1 user thanked author for this post.
-
-
Are Patch Tuesday updates tested prior to release on systems that have installed third-party software?
There is no QA team at Microsoft any more, so no tests are done, and judging from the last 4 years no data is shared with 3rd party hardware and software vendors either.
Just out of interest how do you know that Microsoft don’t have a QA team?
Sounds absurd, although nothing would surprise me.
Microsoft fired it’s QA team in 2015.
Microsoft claims 10 million ‘fans’ help it test Windows 10, but it’s sure got a funny definition of that word
And since Microsoft fired a significant percentage of the QA team that used to be responsible for finding and fixing these bugs, it’s not catching them internally the way it used to.
-
-
-
-
Thanks for the post on this topic. I have noticed that
2019-08 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4512506)
keeps popping up as an important update in this latest batch, and while it has now been uploaded successfully 8 times it is still there for upload.
Today the McAfee Vulnerability scanner is highlighting it as an issue now too.
Any idea what is going on with this and how to rectify?
Thanks
ACER E1-572 8GB RAM Intel Core i7 64-bit Win 8.1 Home Premium Office 2013.
ASUS GL702VS 24GB RAM Intel Core i7 64 bit Win 10 Home 1903 Office 2016.
LENOVO Yoga 310 4GB RAM Intel Celeron 64-bit Win 10 Home 1903.1 user thanked author for this post.
-
-
-
We are at MS-DEFCON 2 (posted at the top) and it is not yet safer to patch. Reports are still coming in — and most describe difficulties in either installation or system operations.
When MS-DEFCON 3 is posted, it will be advisable to patch with caution.
MS-DEFCON System is here:
https://www.askwoody.com/ms-defcon-system/BetaTest {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox85.0b9 WindowsDefender TRV=2004 WuMgr-
It seems that there is no shortage of those who somehow feel the need to be lab rats for M$.
1 user thanked author for this post.
-
-
-
? says;
short answer, don’t uninstall the March version and then install the august version.
long answer:
scroll down to “Current Status,” quote #2.
#1 and #3 speak to the other required components (KB4490628) and (KB3133977)
1 user thanked author for this post.
-
-
Question – a bit late though…
I am just now preparing my Win 7 computers for the Defcon 3 updates, and I find that I don’t seem to have KB3133977 on one of them. Should I go ahead and download that separately before any others? No idea why I don’t have it – I have 5 others within that March 2016 timeframe, but not that one. Also – no KB3125574.
I also wondered about this post which seems to indicate that on older computers – mine is about 10 years old now – that KB3133977 isn’t needed: https://www.askwoody.com/forums/topic/ms-defcon-3-time-to-get-the-august-2019-patches-installed/#post-1941268
Perhaps that is why I don’t have it?
Thanks for the clarification.
-
-
-
-
-
-
-
Sorry it’s a false alarm, my pc crashed because of my wi-fi card once again…
I installed the 3 updates and no problem since then.
Thanks again !!
1 user thanked author for this post.
-
-
-
-
My work PC also seems to be having the second issue described above – when I plug in a thumb drive, I get the device setup dialog, the progress bar stops and the dialog just stays there. The device setup dialog also seems to have a delayed reaction – instead of appearing as when the device is first plugged in, it appears a few minutes later.
This PC is also running Windows 8.1 64-bit. Instead of KB4512488, it has the preview of that update (KB4507463) that was released on July 16. I’m not sure why IT pushed the preview from July instead of the August rollup (considering they pushed it on August 23). On my home PC I don’t install the previews.
-
-
-
Viewing 57 reply threads
Welcome to our unique respite from the madness.
It's easy to post questions about Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Questions? Contact Customer Support.
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. Click here for details and to sign up.
Recent Replies
PFC on Windows Defender In Win 10 Concern
16 minutes agoRick Corbett on PNY Flash Drive Problem
33 minutes agosatrow on Hard Drive at 100% usage
43 minutes ago- 45 minutes ago
dmitriy1980 on Hard Drive at 100% usage
55 minutes ago- 59 minutes ago
b on Susan recommending version 2004
1 hour, 5 minutes agoBob99 on Susan recommending version 2004
1 hour, 19 minutes agoWSjfsharp on Why won’t Task Scheduler launch Office product
1 hour, 21 minutes ago- 1 hour, 24 minutes ago
powerbiz on Doesn’t like external FAT32 HDD
1 hour, 33 minutes agoTex265 on Susan recommending version 2004
1 hour, 36 minutes agoopti1 on Find the cable modem that’s just right for your ISP
1 hour, 39 minutes ago- 1 hour, 40 minutes ago
OscarCP on Apple to block sideloading iOS apps on M1
1 hour, 42 minutes ago- 1 hour, 44 minutes ago
joep517 on Why won’t Task Scheduler launch Office product
1 hour, 45 minutes ago- 1 hour, 47 minutes ago
- 1 hour, 53 minutes ago
WShlewton on Windows Defender In Win 10 Concern
1 hour, 58 minutes ago- 2 hours, 7 minutes ago
- 2 hours, 10 minutes ago
johnf on Hard Drive at 100% usage
2 hours, 11 minutes ago- 2 hours, 11 minutes ago
Susan Bradley on Wow! Even more Office updates!
2 hours, 17 minutes ago- 2 hours, 18 minutes ago
- 2 hours, 18 minutes ago
LoneWolf on Attention partners Microsoft really is coming for your clients this time
2 hours, 18 minutes agoJohn18 on Susan recommending version 2004
2 hours, 21 minutes ago- 2 hours, 21 minutes ago