Windows 7

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

Known Issues for Windows Security Updates for May 2018

As has been the case for a while, Microsoft delivers its OS updates already knowing that there are potential gotchas included. This month, you can expect the following… Windows 10 version 1709 – KB4103727 (OS Build 16299.431) – Some non-English platforms may display the following string in English instead of the localized language: ”Reading scheduled jobs from file is not supported in this language mode.” This error appears when you try to read the scheduled jobs you’ve created and Device Guard is enabled. Windows 7 SP1 and Windows Server 2008 R2 SP1 – KB4103718 (Monthly Rollup) and KB4103712 (Security-only update) – A stop error occurs on computers that don’t support Streaming Single Instructions Multiple Data (SIMD) Extensions 2 (SSE2). For both ...

Microsoft Replaces KB4093118 to Resolve Replaced NICs and Missing IP Addresses

After another embarrassing round of patches this month, particularly for KB4093118 which reintroduced a problem with replacing network information, Microsoft has now delivered a fix. KB4093118 has now been replaced and refreshed and the glaring “known issues” section has been updated. Microsoft says that a Resync is required to get newer revision of this KB for WSUS environment. Microsoft was quick to resolve this problem this month. In past months the company has waiting until last light of the month or pushed fixes until it could solve them during the next Patch Tuesday.   Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

Its Back: April 2018 Update Brings Back Issue that Replaces NIC Settings and Lost Static IP Addresses

UPDATE, April 13, 2018: Microsoft Replaces KB4093118 to Resolve Replaced NICs and Missing IP Addresses Original article… Like a bad odor in old fabric, Microsoft has reintroduced an issue that just won’t seem to go away. One that has caused many customers pains this year. When first delivered on Patch Tuesday for April 2018, KB4093118‘s only known issues were only memory leaks and bluescreens, and that’s bad enough. However, Microsoft has now two days later updated the known issues list (KB4093118) to include the recurrence of the bad NIC problem. A new Ethernet Network Interface Card (NIC) that has default settings may replace the previously existing NIC, causing network issues after you apply this update. Any custom settings on the previous NIC persist in the regi...