The newest Patch Tuesday replace from Microsoft included a number of crucial safety fixes. Unfortunately, as Microsoft has now confirmed, it additionally borked some issues. If you have not utilized that August 13 replace and are operating on Windows 10, Windows 8.1 or Windows 7, chances are you’ll wish to learn this earlier than you do.
What’s the issue with the most recent Patch Tuesday Windows replace?
Microsoft has confirmed a bunch of “known issues” with the August 13 Windows replace. Some, such because the “black screen during first logon after installing updates” subject, have hit customers after earlier updates. That will be filed within the annoying however finally not a lot to fret about folder: it solely impacts a “small number” of customers and solely the primary time they logon after the replace.
Anything that impacts tens of millions of customers is a much more critical factor. And so it’s that Microsoft has confirmed that this Patch Tuesday replace does simply that.
“After installing this update, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an “invalid process name error,” Microsoft has acknowledged.
Don’t assume that VB6 is not one thing that considerations you as a non-programmer Windows person. It virtually definitely does in the event you, or your group, use Microsoft Office. VBA apps together with VB6 nonetheless energy Office scripts, macros and processes which can be important for a lot of companies.
Which variations of Windows are impacted?
The subject has been discovered to have an effect on customers of the next Windows variations:
Windows 7 and Windows Server 2008 R2, Windows 8.1 and Windows Server 2012 R2, Windows 10 model 1507, Windows 10 model 1607 and Windows Server 2016, Windows 10 model 1703, Windows 10 model 1709, Windows 10 model 1803, Windows 10 model 1809 and Windows Server 2019, Windows 10 model 1903 and Windows Server 1903.
What is Microsoft doing about it?
Good query. Kay Ewbank, writing at i-programmer reported that “The Visual Studio weblog has been remarkably quiet about the issue, posting an merchandise about template search in Visual Studio, however nothing about how Microsoft has brought about grief for a big majority of Visual Basic builders.”
Microsoft has stated that it “is engaged on a decision,” and estimates the fix will be available “within the coming days.” As an optional update, users who find their Windows experience broken by the Patch Tuesday update will have to manually “examine for updates” to use it. The irony that, for a lot of, the replace inflicting the grief was put in robotically will not be misplaced on me.
Martin Brinkmann at Ghacks has now reported that Microsoft has began rolling out the fixes for the Visual Basic issues that had been launched with the Windows August 13 Patch Tuesday replace.
It’s not all excellent news, nonetheless. Updates are solely obtainable for Windows 7 SP1 and Windows Server 2008 R2 SP1, Windows 8.1 and Windows Server 2012 R2 and Windows 10 model 1709 (which reached finish of service on April 9.) As already talked about, customers should manually examine for updates and obtain them from the Microsoft Update Catalog with a purpose to set up them. However, no less than these customers have the choice.
“It is unclear why updates for different supported Windows 10 variations weren’t launched as effectively,” Brinkmann stated.
According to Bleeping Computer, “We ought to count on new updates for Windows 10 model 1809 and 1903 to be launched by the tip of the month. The Windows 10 1903 replace will most certainly first be examined by Windows Insiders earlier than being launched to most of the people.”
Why is that this a safety downside?
I am a safety man. I’ve been a safety man since earlier than the Internet was even a factor for most individuals. I encourage everybody to put in the most recent Windows Update as quickly as doable to mitigate towards crucial safety vulnerabilities reminiscent of the brand new wormable distant code execution duo that led to Microsoft urging prospects to patch as rapidly as doable. Or how in regards to the associated BlueKeep risk that led to the NSA issuing an replace now warning to Windows customers?
However, it’s changing into more and more troublesome to put on my safety man hat within the face of updates that freeze Windows or crash your PC. Worse but, some Windows updates have even damaged safety features.
Please do not suppose that I am a Microsoft hater as that could be very removed from the reality. I’m a Windows 10 person myself, and I recognize the complexity of sustaining such a behemoth of code. However, that does not cease me from pondering that Microsoft can certainly do higher.
Why was this newest subject with Visual Basic not uncovered throughout testing earlier than the replace was rolled out to everybody? An group the dimensions of Microsoft, with the assets it has at hand, ought to have high quality testing processes which can be market-leading.
This is a safety downside as a result of it makes individuals suppose twice earlier than making use of updates which can be important from that safety perspective. I am not even speaking in regards to the organizations that may implement some reasoned danger evaluation that balances the risk publicity towards the enterprise continuity. Instead, I am speaking in regards to the tons of of tens of millions of unusual Windows customers who will see the updates breaking stuff and change them off the place they will.
These are the exact same customers who’re most in danger from the vulnerabilities that get mounted in these updates. These are the customers for whom safety is not entrance and middle when utilizing their computer systems; getting the duty at hand, no matter it might be, achieved is all that issues.
Updated August 18, 2019: News relating to the rolling out of Microsoft fixes for the Visual Basic points added.
Get more stuff like this
Subscribe to our mailing list and get interesting stuff and updates to your email inbox.
Thank you for subscribing.
Something went wrong.