Windows 7

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

Microsoft Ends Its Program to Deliver Instant Fixes to Windows Problems

In a redirect from a KB article, Microsoft gives more evidence that it’s truly serious that it wants cumulative updates to be the go-to solution for updates. One page, originally titled “How to use Microsoft easy fix solutions” is now brandished in bold letters: Microsoft Easy Fix solutions are no longer supported It goes on to say… You might have tried to download a Microsoft Easy Fix solution (formerly referred to as a “Fix It”). Easy Fix solutions are no longer supported or offered for download.    

Microsoft Announces Its Next Windows Desktop – in the Cloud

Many people wonder where Windows will go next. Those in attendance for the opening keynote at Microsoft Ignite 2018, might have wondered where any news about Windows desktop would come in.  Technically, it didn’t. Keynotes are supposed to be visionary speeches. But, when a vendor owns the conference, it becomes a tell-tale sign of where the company wants to herd its customers next so that it can optimize its revenue base for the future. So, the bigger news in a vendor keynote is what is NOT mentioned. Microsoft’s CEO, Satya Nadella, used today’s keynote to talk about the cloud and AI. What was not mentioned during the opening keynote was Windows on PCs. However, Windows hasn’t been left out entirely from Ignite news. Instead, Windows was given new life – but i...

Microsoft Service Stack Updates Will be Recategorized as Security Updates so Customers Will Actually Install Them

The confusion around the many updates that Microsoft delivers each month continues. But, the company is trying to hard to minimize the confusion – if it can’t simply fix the quality. However, a new explanation from Microsoft, seems to suggest that the company has found a culprit for the many quality related complaints from customers about its monthly updates. In short, its the customers. The culprit (at least for Windows 7 customers) is that many customers are skipping the Servicing Stack updates. These updates, Microsoft says, are designed to… …ensure that you have a robust and reliable servicing stack so that your devices receive and install Microsoft security fixes. So, without these installed, many security updates are being installed into a questionable updatin...

Intune to Stop Supporting Windows 7 in 2020

Microsoft has taken to its notification system to give advanced warning to customers still managing Windows 7 devices. Windows 7 reaches the end of extended support on January 14, 2020. As such, Microsoft will also stop supporting management of Windows 7 devices using Intune (or whatever it is called in 2020). Windows 7 reaches end of extended support on January 14, 2020. At that time, Intune will retire support for devices running Windows 7, so we can focus our investment on supporting newer technologies and providing great new end user experiences. After that date, technical assistance and automatic updates that help protect your PC will no longer be available. Microsoft strongly recommends that you move to Windows 10 before January 2020, to avoid a scenario where you need service or sup...

NIC Stops Working Issue for Windows 7 Roll-up Survives Another Month

This nagging issue has been around for a couple months now, but Windows 7 users can still expect it in certain situations. Microsoft is not fully aware of the exact configurations that cause it, but in those unknown states the Network Interface can stop working after installing the Windows 7 Roll-up. This month’s roll-up: September 11, 2018—KB4457144 (Monthly Rollup) Issue: 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. Workaround: To locate the network device, launch devmgmt.msc. It may appear under Other Devices. To automatically rediscover the NIC and install drivers, se...

Monthly Rollup for Windows 7 Causes the Network Controller to Stop Working

Something to be aware of with the monthly rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB4338818) for July 10, 2018. There is an issue with Windows and third-party software related to a missing file (oem<number>.inf). Because of this issue, after you apply this update, the network interface controller will stop working. The Microsoft supplied workaround: 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.   a. Alternatively, install the drivers for the network device by right-clicking the device and selecting Update. Then select Search automatically for updated driver software or Browse my computer for driver software.  ...