Your company's ad could live here and reach over 50,000 people a month!

Patch Tuesday

February Cumulative Update for Windows 7 Makes it Difficult to Troubleshoot NIC Problems

With the rollout of Microsoft’s monthly updates for Windows 7, a new bug has been introduced that could make troubleshooting network problems more difficult. After installing this update, the Event Viewer may not show some event descriptions for network interface cards (NIC). Microsoft doesn’t go any further in describing exactly what event descriptions are forfeit but does promise a resolution to the issue sometime in March 2019.

Mid-February Slated for Microsoft to Fix Virtual Machines for Windows 7

As has often been the case, Microsoft has introduced a new gotcha this month in the cumulative update for Windows 7. After installing this update, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).” This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures. Microsoft is aware of the issue and has set mid-February as a tentative time to see a fix. Stay close, we’ll keep a watchful eye out and let you know when the fix is available.

February 2019 .NET Update Contains Security Fixes for Domain Spoofing and Remote Code Execution

Many customers try hard not to have to update the .NET code for Windows. These days, some consider every Windows update as a potential timebomb, but the .NET updates have a long history of being a difficult problem child. Microsoft delivered .NET updates for February 2019 and these updates come with some fixes that may cause some to do a double-take. These may warrant some heightened attention. Here is what’s up… CVE-2019-0613 – Remote Code Execution Vulnerability This security update resolves a vulnerability in .NET Framework software if the software does not check the source markup of a file. An attacker who successfully exploits the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on by using administrative user rights,...

Shared Calendar Workarounds for CUs for Exchange 2016 and 2019

According to Microsoft a bug exists in Cumulative Update 1 for Exchange Server 2019 and Cumulative Update 12 for Exchange Server 2016 where users can no longer accept Share Calendars through an email invitation. Microsoft has supplied the following workarounds. Use one of these until a final resolution is available. > Open the invitation from the Notifications pane in Outlook on the web. > Add the shared calendar manually in Outlook on the web. > Open the invitation in Outlook, and then add the shared calendar.  

Microsoft Delivers February Security Updates for Windows 10

The following cumulative updates for Windows 10 are now on the wire: Windows 10 version 1507 KB 4487018 (OS Build 10240.18132): Windows 10 version 1607 KB 4487026 (OS Build 14393.2791): Windows 10 version 1703 KB 4487020 (OS Build 15063.1631): Windows 10 version 1709 KB 4486996 (OS Build 16299.967): Windows 10 version 1803 KB 4487017 (OS Build 17134.590): Windows 10 version 1809 KB 4487044 (OS Build 17763.316): In these updates, Microsoft still has not addressed the problem with Microsoft Edge where users cannot navigate local PC web pa...

Microsoft Confirms DNS Issue at Fault for Windows 10 Update Problems

A recent problem with Windows’ ability to update had both customers and Microsoft scrambling to pinpoint the cause. After research into the problem, Microsoft identified a global DNS corruption that led to a major outage. Many customers noticed the issue several hours prior through many other means (product and service failures that also depend on DNS), but the Windows 10 updating problem was the final indicator. Microsoft has now provided an explanation through the Windows 10 History Page… February 4, 2019 9:45 PM PST“The Windows Update service was impacted by a data corruption issue in an external DNS service provider global outage on January 29, 2019. The issue was resolved on the same day and Windows Update is now operating normally, but a few customers have continued ...

Microsoft Makes a New CU Available for Windows 10 1809

What could be the beta version of the cumulative update for February 2019’s Patch Tuesday has been made available. “Seekers” can go get it now by manually checking Windows Update. This new CU contains a slew of fixes for Windows 10 1809, but still contains a couple lingering problems including not able to open Microsoft Access databases and the inability for Microsoft Edge to browse the local computer. January 22, 2019—KB4476976 (OS Build 17763.292) Fix list: Addresses an issue that may cause Microsoft Edge to stop working with certain display drivers. Addresses an issue that may cause third-party applications to have difficulty authenticating hotspots. Addresses an issue that causes promotions of non-root domains to fail with the error, “The replication operation encount...

Microsoft Resolves Access 2010 and Excel 2010 Problems with KB4462157

One issue reported this month for Microsoft’s updates included an issue where Access 2010 and Excel 2010 would stop working after installing KB4461614. Microsoft has now delivered a fix for the problem. The fix is included in KB4462157. This update contains the following improvements and fixes: This update adds support for new Japanese eras in the Japanese calendar. Note To enable this improvement, you must install KB 4461579 together with this update. Fix: After KB 4461614 is applied, Access 2010 and Excel 2010 stop working.

KB4480116 Causes Microsoft Edge to Block Local Browsing

Reports have filtered in that, after installing KB4480116, Microsoft Edge no longer “trusts” local IP addresses – meaning that Edge errors out when attempting to access the local IP address, This doesn’t affect a lot of users so Microsoft isn’t planning to fix the bug until Patch Tuesday for February 2019. It does affect all versions of Windows 10. However, adding the local IP address to the list of trusted sites in Windows 10’s Internet settings resolves the issue.

Microsoft Delivers Fixes for Hotspots for Windows 10 1803, 1709 and 1703 but not for 1809

Microsoft has now begun delivering updates for its updates. On Tuesday, the company delivered new cumulative updates for Windows 10 1803, 1709 and 1703. These updates come just a week after Microsoft’s initial round of fixes for 2019. These updates, in particular, appear to solve a problem introduced during Patch Tuesday week that caused Windows 10 to not authenticate hotspots. Unfortunately, it looks like Windows 10 1809 hasn’t gotten the same treatment yet. Here’s what’s available now: KB4480976, KB4480967 and KB4480959

Microsoft Japan Gives the List of January’s ‘Problematic’ Updates for Windows 7 Network Connectivity

UPDATE: Microsoft quietly resolved the issue described in this article using KB4487345 Original article… Microsoft USA rarely apologizes for bad patches and definitely refuses to concede that any are problematic, however, Microsoft Japan has now listed out the updates (translated page) from January 2019’s Patch Tuesday that are giving companies fits when trying to connect to their networks. What started out as the inability to connect to network shares has also been reported to keep users from connecting to shared printers. After applying one of the following update programs published on January 8, 2019, to the file server and accessing the file server (the computer holding the shared folder ) by using the local user belonging to the Administrators group, The event of connectio...

CVE-2019-0543 Changes How Windows PowerShell and PowerShell Core 6 WinRM Based Remoting Works

If you’re attempting to do loopback remoting for Windows PowerShell or PowerShell Core 6 after applying January security updates, you may have run into problems. Per Microsoft… The breaking change is not in PowerShell but in a system security fix that restricts process creation between Windows sessions. This fix is preventing WinRM (which PowerShell uses as a remoting transport and host) from successfully creating the remote session host, for this particular scenario. There are no plans to update WinRM. Further… The breaking change only affects local loopback remoting, which is a PowerShell remote connection made back to the same machine, while using non-Administrator credentials. Details and workaround: Windows Security change affecting PowerShell