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

Windows 7

Known Issues (so far) for March 2019 Patch Tuesday Updates

Each month Microsoft prepares customers for the problems it knows about when delivering the bevy of updates designed to make its software more secure.  These are things that the company identified during testing and will likely fix later. However, the first 24 hours are crucial, as customers tend to locate and report on the stack of unknown issues that couldn’t be detected during testing. Here’s what Microsoft has communicated already… 4489878 Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1 (Monthly Rollup) – After installing this update, Internet Explorer 10 may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop...

Windows 7 to Start Nagging Users to Upgrade Starting in April

Support for Windows 7 ends on January 14, 2020, and as Microsoft did with Windows XP, the company will start using nag banners to get users to upgrade. In this case, the upgrade point is to Windows 10. To help our customers get advanced notice of this change, we are reaching out with information and resources. Beginning next month, if you are a Windows 7 customer, you can expect to see a notification appear on your Windows 7 PC. This is a courtesy reminder that you can expect to see a handful of times in 2019. By starting the reminders now, our hope is that you have time to plan and prepare for this transition. These notifications are designed to help provide information only and if you would prefer not to receive them again, you’ll be able to select an option for “do not notify me again,”...

With a Serious Exploit Being Actively Targeted Against Windows 7, Google Pushes Windows 10 Upgrades

Google recently patched a zero-day flaw in its Chrome web browser, but a second one that affects Windows 7 is still being actively exploited. Google relayed the information about the vulnerability to Microsoft, and the Windows company has responded directly to Google that a fix is in the works. Of course, there’s no timeline given, so Windows 7 users are vulnerable. Based on the vulnerability that only affects Windows 7, Google is providing this guidance: As mitigation advice for this vulnerability users should consider upgrading to Windows 10 if they are still running an older version of Windows and to apply Windows patches from Microsoft when they become available. We will update this post when they are available. Details: Disclosing vulnerabilities to protect users across platform...

Workplace Join for non-Windows 10 Computers

Microsoft has provided an installation tool for non-Windows 10 computers to enjoy self-service registration on the corporate domain. The tool is distributed through an .MSI file and is available for download: Microsoft Workplace Join for non-Windows 10 computers The tool allows you to register non-Windows 10 computers for Workplace Join and supports the following non-Windows 10 systems: Windows 7, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

Microsoft to Begin Upgrading Windows 7 Security in March 2019

In November 2018, Microsoft communicated upcoming changes to Windows 7 security, moving to the SHA-2 algorithm exclusively. We now know the timeline for these changes. The company will deploy the changes methodically, but start the process with March 2019 updates and finishing up in July 2019. Customers running legacy OS versions (Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2008 SP2) will be required to have SHA-2 code signing support installed on their devices by July 2019. Any devices without SHA-2 support will not be offered Windows updates after July 2019. To help prepare you for this change, we will release support for SHA-2 signing in 2019. Some older versions of Windows Server Update Services (WSUS) will also receive SHA-2 support to properly deliver SHA-2 signed up...

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.

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...

Microsoft Reverts Changes to KMS Servers that Caused Widespread Problems with KB971033

UPDATE: What seemed like yet another problem with yet another Microsoft patch has turned out to be something else. The issue, as it turns out, was a combination of customers installing KB971033 and Microsoft making changes to its license activation servers. From Activation failures and “not genuine” notifications around January 8, 2019, on volume-licensed Windows 7 KMS clients: A recent update to the Microsoft Activation and Validation unintentionally caused a “not genuine” error on volume-licensed Windows 7 clients that had KB 971033 installed. The change was introduced at 10:00:00 UTC on January 8, 2019, and was reverted at 4:30:00 UTC on January 9, 2019. Note This timing coincides with the release of the “1B” January 2019 updates (KB 4480960 and KB 4480970) that ...

Microsoft Acknowledges KB4480970 Bug for SMBv2 Shares, Provides Explanation and Guidance

Customers are experiencing a severe bug in KB4480970 where computers are unable to access network shares. Reports have been rolling in steadily since the roll-up for Windows 7 was released. Microsoft has now updated the roll-up history page to reflect the bug, issue some reasoning, and apply some guidance for affected customers. Problem: Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local “Administrators” group. Guidance: To work around this issue use either a local account that is not part of the local “Administrators” group or any domain user (including domain administrato...

2018 Holdover Bug Causing Renewed Problems with Network Connectivity for Windows 7

A bug that has existed for much of 2018 for Windows 7 and Windows 2008 R2 has once again begun causing problems for users of those operating system versions. The original bug forced many to reinstall hardware drivers for their network cards… After you apply this update, the network interface controller may stop working on some client software configurations. This occurs because of an issue related to a missing file, oem<number>.inf. The exact problematic configurations are currently unknown. To locate the network device, launch devmgmt.msc. It may appear under Other Devices. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu. Alternatively, install the drivers for the network device by right-clicking the device and cho...

Tip: Curated List of Servicing Stack Updates

Microsoft has now produced a page that attempts to centralize communication about the most current Servicing Stack Updates. This is a list of the latest servicing stack updates for each operating system. This list will be updated whenever a new servicing stack update is released. It is important to install the latest servicing stack update. Page: Latest Servicing Stack Updates

  • 1
  • 2
  • 6