Win7 Updates cause loss of Network Connectivity

Topic

New Reply

Topic Created on behalf of @Morty

May Patches 2019:
I’m running Microsoft Windows 7 Professional, Version 6.1.7601 Service Pack 1 Build 7601
System Type: x64-based PC with Microsoft Security Essentials automatically updated daily.
I did a full backup the other night, then ran the update yesterday afternoon.

After I restarted the computer, I got the message that I installed new updates. Then I got another message: I had no internet connection. I ran the troubleshooter and it told me I had no Ethernet connection because I had no driver. And it couldn’t find any driver or solution.
I tried rebooting but that didn’t help.
Finally, I ran a system restore and undid the update.

June patches 2019:
Sigh. It happened again. Second month in a row I updated and lost my network connection. (More than you want to know at https://www.askwoody.com/forums/topic/ms-defcon-3-get-windows-xp-win7-and-associated-servers-patched/#post-1656812)
Once again, I had to do a system restore to get on to the net.

PC Specs:
Processor: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date    Dell Inc. A11, Fri 12/30/11
Intel(R) HD Graphics
PNP Device ID    PCI\VEN_8086&DEV_0102&SUBSYS_047E1028&REV_09\3&11583659&0&10
Adapter Type    Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description    Intel(R) HD Graphics
Adapter RAM    (2,084,569,088) bytes
Installed Drivers    igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32
Driver Version    9.17.10.3517
INF File    oem4.inf (iSNBD0 section)
WAN Miniport (SSTP)
Adapter Type    Not Available
Product Type    WAN Miniport (SSTP)
Installed    Yes
PNP Device ID    ROOT\MS_SSTPMINIPORT\0000
Service Name    RasSstp
IP Address    Not Available
IP Subnet    Not Available
Default IP Gateway    Not Available
DHCP Enabled    No
DHCP Server    Not Available
DHCP Lease Expires    Not Available
DHCP Lease Obtained    Not Available
MAC Address    Not Available
Driver    c:\windows\system32\drivers\rassstp.sys (6.1.7600.16385, 82.00 KB)
Name    [00000001] WAN Miniport (IKEv2)
Adapter Type    Not Available
Product Type    WAN Miniport (IKEv2)
Installed    Yes
PNP Device ID    ROOT\MS_AGILEVPNMINIPORT\0000
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Driver date: Thu 02/21/13
Driver version: 12.6.45.0

Information taken from previous posts by @Morty
Help and advice to solve this issue would be appreciated

If debian is good enough for NASA...

5 users thanked author for this post.

SueW, Myst, Elly, Morty, PKCano

Reply | Quote

Replies

Thank you!

I may not have friends in Redmond, but I sure do at Woody’s! Bless all of you.

The question remains, if this doesn’t get straightened out, do I have to bite the bullet and “upgrade” to Windows 10? (I just gave up XP last year when the box went on me.)

2 users thanked author for this post.

Myst, Microfix

Reply | Quote

@Morty, Try the following:
Step 1 – Look for an updated NIC driver (or the most recent) from dell for your PC /Model to download and save somewhere, then install the June patch.

UPDATE: It looks like your NIC driver has been updated Version: 24.1 (Latest) Date: 6/27/2019, download the ‘PROwinx64legacy’ driver from:
https://downloadcenter.intel.com/download/18713/Ethernet-Intel-Network-Adapter-Driver-for-Windows-7-?product=47549

Step 2 – Once the June 2019 patch is installed, go to device manager and roll-back the NIC driver.
IIRC, this was MSFT’s workaround from March/April 2018 and seems like your NIC is affected in some way.

Step 3 – If Step 2 is unsuccessful, install the ‘PROwinx64legacy’ driver that you downloaded (with june patches already installed)

If debian is good enough for NASA...

1 user thanked author for this post.

Morty

Reply | Quote

@microfix said

…Step 2 – Once the June 2019 patch is installed, go to device manager and roll-back the NIC driver.
IIRC, this was MSFT’s workaround from March/April 2018 and seems like your NIC is affected in some way. …

Here’s what MS actually said, below, so your memory’s not too far off! 🙂

From @mbhelwig ‘s post number 335959

To locate the network device, launch devmgmt.msc. It may appear under Other Devices.
1. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
2. Alternatively, install the drivers for the network device by right-clicking the device and choosing Update. Then choose Search automatically for updated driver software or
Browse my computer for driver software.

His post quotes directly from MS’s bulletin for KB4480970, which was issued while the monthly rollups were still knocking folks’ network cards out on a seemingly random basis. The above quote that @mbhelwig used was included in practically every MS page for the monthly Win7 rollups from March 2018 until earlier this year, if I recall correctly (IIRC).

 

1 user thanked author for this post.

Morty

Reply | Quote

Hi Morty, “anonymous 6536” here. You have good people helping you, I hope Cybertooth comes in.

From last month, I mentioned the below. You might want to let DELL scan your computer for the Network driver and see if there is a newer one. Or go to DELL’s website, support, and put in your Service TAG Number and look yourself at the options/drivers offered. Dell is usually VERY easy to find drivers.

Last month you mentioned: your on a Dell (you said previously – BIOS Version/Date Dell Inc. A11, Fri 12/30/11).

Drivers:
Intel Site:
https://downloadcenter.intel.com/product/47549/Intel-82579-Gigabit-Ethernet-Controller
Intel Network Adapter Driver for Windows 7 Version: 23.5.2 (Latest) Date: 2/6/2019, 54.44 MB

Windows Catalog: (this is what you probably have an MS driver being version 12…)
Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection (64bit)
Windows 7,Windows Server 2008 R2, 11/12/2015 12.15.31.0 608 KB
https://www.catalog.update.microsoft.com/Search.aspx?q=82579LM

I would try DELL first.

Good luck Morty.

1 user thanked author for this post.

Morty

Reply | Quote

Thank you all and bless you!

I can’t work on this today. Hopefully, Sunday or Monday.

All the best,

Morty

Reply | Quote

@ Morty

Morty wrote:

The question remains, if this doesn’t get straightened out, do I have to bite the bullet and “upgrade” to Windows 10?

Firstly–with a little bit of effort–I’m pretty sure your loss of network connectivity can be worked out.

Secondly–upgrading to Win 10 will not be a panacea! It will be, for you, an unfamiliar Operating System (OS) that will have you stumbling around looking for what you want to configure to your liking. And, it has its own updating problems that may be far worse than loosing your network connectivity to the internet. How about a system that will not boot–and unless you know the *secrets* as to how to boot to the *emergency repair* console–are you going to be comfortable with that?!

Right now, you just needed to have a *Restore Point* created, and knowing how to restore that to get back to a functional system.

In terms of solving your current problem–if you jump through the hoops of figuring out how to download a copy of the driver for your network card, and knowing how to install it–your problem will most likely be solved.

If necessary, you might have to try installing a replacement network card (you, or someone else, or a repair facility), and installing its driver that comes with that new card.

Or, it may be a case where you can get a USB network wireless adapter that you plug into a USB port–but, you will still have to install the needed driver software (unless there’s a generic driver from Microsoft that’s part of the Win7 installed drivers).

Looking at the various posts that have been made for last month’s and this month’s updates to your posting about the problems you have been having, I’ve seen any number of suggestions having been made as to how to fix your problem. Most have been regarding figuring out what driver you need, if you can access Dell to get the appropriate driver, and to install the driver. But, I’ve seen no response from you to indicate that you have followed through on those suggestions.

That being the case, I have the sense that you really do not understand what’s being suggested that you do, I’m guessing that you’re uncomfortable proceeding because you don’t feel you know what you’re doing, and probably afraid you’re going to *break* something, and you will not know how to deal with it.

I have to be away from the computer for awhile, so will not be able to respond until later today or this evening. But a couple questions to get started–then we can look at step-by-step instructions as to how to proceed:

1. Do you have a Dell computer?

2. Is it a desktop?

3. Do you know what a *Service Tag* for a Dell computer is?

4. If you have a desktop, I would expect the Service Tag to probably be on the back of the tower where all the ports and wires are connected. If you find that Tag, post the numbers and letters here. We can then look for the correct network driver for your system.

Be back later.

1 user thanked author for this post.

Morty

Reply | Quote

[Morty]

Just Lurking wrote:

1. Do you have a Dell computer? 2. Is it a desktop? 3. Do you know what a *Service Tag* for a Dell computer is? 4. If you have a desktop, I would expect the Service Tag to probably be on the back of the tower where all the ports and wires are connected. If you find that Tag, post the numbers and letters here. We can then look for the correct network driver for your system.

Hi and thank you again! Had to wait for a break from editing to do this….

Yes, it’s a Dell desktop. (I never made friends with laptop keyboards and touch pads.) The service tag on the back, if these old eyeballs read it correctly, is 62R9PS1.

“Uncomfortable” is putting it mildly. I haven’t had so much fun since I spent a few hours years ago getting picking pieces of debris out of my registry from a bad install of an overrated antivirus program. It’s like doing root canal work on myself. Without anesthesia.

Since then, I leave the registry to experts. (I do use Revo Uninstaller, set to moderate, but I let it do the work and hope for the best.)

Bless you.

Morty

• This reply was modified 5 years, 8 months ago by Morty.

Reply | Quote

? says:

hi morty,

if you have an optiplex 990 per your service tag then here is a link for drivers:

https://www.dell.com/support/home/us/en/04/product-support/servicetag/62r9ps1/drivers

i get mine from intel (driver only not the full monty). i hope you get the problem worked out to your liking soon

 

1 user thanked author for this post.

Morty

Reply | Quote

Thank you!

If I did a full backup last week, do you think I need to go through the whole drill again before trying this?
OK, I know, I know. Don’t mess. So I’ll do a backup tonight and then bite the bullet tomorrow (and pray).

Reply | Quote

Yes, make your backup. Just because.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

Morty

Reply | Quote

I hear you! You have to be crazy not to be paranoid.

Reply | Quote

Hi Morty, “anonymous 6536” here. You have good people helping you, I hope Cybertooth sees this too.

NightOwl, another Anonymous and others have good info. The site to DELL given by Anon
#1871781 looks good.

I see the “Intel 825xx 10/100/1000 Ethernet Controller Driver” and also see the “Intel Chipset Driver” that you might want to consider (for motherboard update) IF all goes well with your Network Driver update.

Keep us posted Morty.

1 user thanked author for this post.

Morty

Reply | Quote

Thanks again to all of you.

Pardon my ignorance, but why would I want to update my motherboard? Isn’t it just the network that I have to worry about?

Reply | Quote

In most cases the Network Adapter [NIC] is part of the motherboard.  You could get a PCI or PCIe card to plug in and set the BIOS to Disable the onboard adapter.

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

1 user thanked author for this post.

Morty

Reply | Quote

Aha.

Reply | Quote

[Bob99]

Hi Morty!

Great to see you’ve been able to kind of peck away at the issue.

With all due respect to @NightOwl who’s a great resource for troubleshooting, I’ve read your posts from the first ones back in May when this first happened to you, so I know what you’ve been told to do over quite a bit of time.

I would stick with trying to get the latest network driver from Dell’s site because they’re the ones who produced your computer and who specified which chipset and which chips were to be put on your computer’s motherboard. Because of this, they’re the ones who know best which is the correct and truly latest driver for anything that is soldered to your motherboard, as the networking chip from Intel is. So follow the advice of those above pointing you to the Dell site for your computer. Here’s a direct quote of what Intel says about using their (Intel) drivers for Intel chips in systems from major computer makers, such as Dell:

About Intel® drivers

The driver or software for your Intel® component might have been changed or replaced by the computer manufacturer. We recommend you work with your computer manufacturer before installing our driver so you don’t lose features or customizations.

 

Once you have that driver from Dell), tuck it away in a safe place, just in case you need it later, but don’t install it or run it just yet. By the way, the safe place can be a folder on your computer’s internal hard drive, but a better place would be a flash drive or an external hard drive that your computer can see without your having to do anything special.

We want to see if you can get Windows to work with your current driver by “re-discovering” it, in the next step below.

Once you’ve made a known-good backup, and it sounds like you already have, then go ahead and take the plunge to install the June Security Monthly Quality Rollup (KB4503292). If past history is any guide, this will nail your networking card right between the eyes. As you’ve asked repeatedly before (possibly even in the throes of exasperation) “So now what??”

The answer is, try following Microsoft’s guidance that I quoted in my post towards the beginning of this thread in post #1868807.

That post, by the way, quotes from a previous post in one of the other threads you’ve posed this question on by @mbhelwig . It also might be a good idea to bring that post up in the middle of the screen and then either highlight it and print it out, or do a screen capture and save it that way, just so you have something to follow without having to be online, since you probably won’t have your networking card available until after the procedure.

If you’re not sure about something in the instructions from Microsoft, please feel free to ask, as always! Questions are always very welcome here at AskWoody!

Either one of Microsoft’s methods should work to get your networking card back up and running. If they fail, then it will be time to install the latest driver for your networking chip from Dell, and try again. That’s where @NightOwl’s vast knowledge will be able to help you through that procedure…the right way the first time! 🙂

I do hope that @Cybertooth drops in on this thread, as he’s also been of some very good help to you in the other threads, as has your other friend, “anonymous 6536”.

R/

Bob99

 

• This reply was modified 5 years, 8 months ago by Bob99. Reason: Clarify post and add instructions

1 user thanked author for this post.

Morty

Reply | Quote

Sounds like a plan.

I’ll try to run a backup before going to bed tonight. Then I’ll try this again some time after the dawn’s early light.

Thank you all again!

And yes, it would be nice to hear from @cybertooth again.

All the best,

Morty

Reply | Quote

@ Morty

Sorry–I was not available earlier today to reply to this thread ….

1. Are you in a hurry to apply the June Update? Are you desperate to get it done?

Just so you realize it–Woody has put his MS-DEFCON level to 2 now–no longer 4. So tomorrow morning is *Patch Tuesday* when you plan to apply the Update–it will likely be the new July cumulative update which has not been approved as *ready* for applying to our systems that you will see (unless you happen to be able to sneak in under the wire before Microsoft releases the new Updates).

If you are *desperate*–there is a secret way to still get the June Cumulative Update–you have to jump through some hoops–but it can be done. But, I would take it slow at this point, and do some *preparations* to make sure you are ready to deal with any loss of Network connectivity.

Morty wrote:

“Uncomfortable” is putting it mildly.

2. I have looked at all the Replies made today–and I do not see any indication that you have visited the Dell Support website, have entered your Service Tag ID, have found the Network driver, and have downloaded it.

So, have you done any or all of the above? If you have done all the above, please so state so I (and we all) know that you have done so. If you have not done all the above–you’re not ready yet.

If you have not done the above, I (we) need to take you through a step by step outline so you are comfortable with what needs to be done.

And, if you are not ready yet, you should not *rush* things.

Yes, the Updates need to be done. The May, and now the June Updates should have the *Remote Desktop Bluekeep* software hole patch in them which is significant, but as of yet there does not appear to any active threat. If you have never uses Remote Desktop, it should probably be inactive by default, and you are not likely to be a target. So, if that’s true–you probably do not need to sweat bullets just yet.

You have already attempted to apply both the May and the June Updates, and both have made your Network connectivity go away. So doing it again without a clear plan of what to do next after applying the update may not get you very far.

So, for the record, I was going to recommend that you download and go through the steps of updating you Network driver to the last most recent driver released by Dell–looks like that version date is going to be in 2013 (yes, you have an older Dell system, and they have stopped putting out more recent updates–Intel might offer a more recent driver, but let’s not go there just yet), but it’s newer than what you currently have.

Once you have been through the process of installing a Network driver, you will be ready to do the same again if installing the update breaks the Network connectivity.

And, we can test *Reverting* to a previous Network driver to see if that procedure works on your system.

By the way, installing an updated Network driver has the same potential risk that all updating has–it might break your Network connectivity–so we will want all the same safeguards in place–a system image backup, a current Restore Point (do you know how to manually create a Restore Point–as opposed to the automatic one that Windows Update creates for you?), and a downloaded Network driver from Dell available for installing.

Bob99 wrote:

As you’ve asked repeatedly before (possibly even in the throes of exasperation) “So now what??”

The answer is, try following Microsoft’s guidance that I quoted in my post towards the beginning of this thread in post #1868807.

That post, by the way, quotes from a previous post in one of the other threads you’ve posed this question on by @mbhelwig . It also might be a good idea to bring that post up in the middle of the screen and then either highlight it and print it out, or do a screen capture and save it that way, just so you have something to follow without having to be online, since you probably won’t have your networking card available until after the procedure.

So, that’s a good recommendation, but what I’m suggesting is that we go through that outline step by step so you know what to look for, and where to look for it. The outline is of no value if you do not truly understand the steps, and you are not comfortable following them.

The outline has a fair bit of technical language that assumes a fair bit of techie background and understanding–if it’s not something you do on a regular basis–it probably is not something you’re going to understand–without seeing the actual steps involved.

1 user thanked author for this post.

Morty

Reply | Quote

@ Morty

Morty wrote:

Pardon my ignorance, but why would I want to update my motherboard?

For most techies–because you can!

Actually–updating something like the motherboard chip set can offer improved operations. Sometimes it allows for new functions, etc.

One can try to find out what improvements the update offers, but often the details are lacking.

1 user thanked author for this post.

Morty

Reply | Quote

@ Morty

Here’s a Service Tag on the bottom of my old Dell Laptop:

If I do a Google Search, I can find this Dell Support result:

If I select the *Drivers and Downloads* link, I go here:

https://www.dell.com/support/home/us/en/04?app=drivers

After I enter the Service Tag ID (7S67971), I end up here:

It’s my Dell Latitude D610 Laptop.

There are no Drivers listed because the laptop only supported WinXP which is no longer a supported OS, and Dell is no longer supporting it’s older laptop.

I was surprised to see the BIOS update being available, when other drivers are no longer offered. But there you have it …

Morty, have you done the above for your Service Tag?

1 user thanked author for this post.

Morty

Reply | Quote

@ Morty

I have not seen a post from you this morning. Hope everything is going okay–especially if you have proceeded with installing the latest Update.

So, using the Service Tag you provided, does this appear to be your System?:

You need to select the drop down menus for *Operating System*, and for the *Category* of driver you wish to look for:

and:

After doing the above, you should now have this driver showing:

You can then use the *Download* link to save a copy of the driver to your computer–if your Desktop is not too crowded, I would probably save it there until you’re done using it. It can then be moved elsewhere for permanent storage for future use if needed.

1 user thanked author for this post.

Morty

Reply | Quote

Just Lurking wrote:

I have not seen a post from you this morning. Hope everything is going okay–especially if you have proceeded with installing the latest Update.

You are terrific! Thank you so much! Indeed, I’m in good hands…..

I’m just catching up on editing and trying to get out a column; can’t stop to check the engine. Hopefully, we’ll get there soon.

I can’t thank you enough. Bless you all!

See you later. Adios, Kemo Sabe

Reply | Quote

@ Morty

I was looking at the various information that’s available on the Dell Support site after entering your Service Tag ID.

One of the sections is the *System Configuration* section:

After clicking on that, you then have a new link to click on–*Components*.

Clicking on that brings up a list of items that was the original system as it left the Dell factory. The next screen shot is only a partial listing, but one item caught my eye:

Clicking on the *triangle* pointing towards that item, displays some additional information:

This information seems to conflict with what has been presented in the first posting of this topic:

Microfix wrote:

May Patches 2019:

I’m running Microsoft Windows 7 Professional, Version 6.1.7601 Service Pack 1 Build 7601
System Type: x64-based PC

The OS that Dell says it installed on your system was Win7 Ultimate, 32 bit. I think you have said in another thread somewhere (I can not remember where), that your system was a *refurbished* Dell system–is that true? Who *refurbished* it? And, does it have a tag of authentication for the OS? What does that tag say?

The above are some curiosity questions to confirm the information about your system.

1 user thanked author for this post.

Morty

Reply | Quote

Thanks again!

Should I download the file now or before I attempt another update? (When we get off DEFCON 2.)

Reply | Quote

[Just Lurking]

@ Morty

To confirm what OS is installed, regardless of what the Authentication Certificate label might say, you can do the following:

Click *Start*, and in the Search Box, type *system information*:

Then click on *System Information* at the top of the resultant list. You will then get the *System Information* program that starts with a *System Summary* page:

What *OS Name* is listed?

What *System Type* is listed?

And, now we will know for sure!

• This reply was modified 5 years, 8 months ago by Just Lurking.
• This reply was modified 5 years, 8 months ago by Just Lurking.
• This reply was modified 5 years, 8 months ago by PKCano.

1 user thanked author for this post.

Morty

Reply | Quote

@ Morty

So, if you followed the corrections indicated above, and you finally got the the *System Information* page–

What *OS Name* is listed?

What *System Type* is listed?

1 user thanked author for this post.

Morty

Reply | Quote

@ Morty

So, I decided to download the driver that Dell is offering you for your Network Driver. Saved it to my Desktop.

The file name is *Network_Driver_NNGMH_WN_18.1.0.0_A08.EXE*, and I clicked it to start the driver install program (you might have to double-click the file depending on how your system is set up–I’m set up for a single-click).

Here’s the initial screen that the installation program presents:

You’re given the choice of either installing the driver, or if you wanted to, you can have the installation program extract the files to your hard drive. I chose the *Install* button, and got this second screen:

There’s no current version for me because I do not have any version of this driver installed on my system. I then selected *Yes* to the question as to whether to install this driver or not, and here’s the result:

The installation failed! Not surprising. I do not have this Network Controller (or NIC–Network Interface Card) on my system. My computer is not a Dell, and I do not have this model Network Controller. So, I expected a failed attempt to install this driver.

Here’s a quote from the Installation Log file:

07/13/19 14:51:11: The user has answered YES to

install driver query. Proceeding to driver

installation.

07/13/19 14:51:21: Installation was not

successful.
The most likely cause is no supported network

connection exists on this platform.

*… most likely cause …* Oh, man! One would think they could be a little more emphatic–they know I don’t have this *network connection* (i.e. controller, or NIC) on my system, but they’re being *politically correct* (polite) by not telling me I’m *stupid* for trying to install their driver!

You, on the other hand, should get a different result–you should get a *successful* install message stating that your Network Controller now has a newer software version.

*****************************************

I’m going to be out of town for the next few days–back late Wed. So I will not be available to answer questions, or talk about *next steps*.

But, given the last few posted Replies that I have made, I think you probably have the necessary steps to download and install the latest Network Controller driver for your system.

Before you attempt the driver update, make sure you have a system image backup. And make sure you create a manual *Restore Point* prior to attempting to do the update.

Once you have those two things in place, single or double click that installation file and follow the prompts.

You should have the updated driver in place once you have completed the steps.

This is the exact same steps you would take if your Network Controller is reported as not having a current driver after you install a Cumulative Update that knocks out the driver for your Network Controller.

When I get back, we can talk about the steps to bring back the June Cumulative Update to test out installing that update to test your ability to recover if it knocks out your driver again like it did recently.

Back in a few days …

1 user thanked author for this post.

Morty

Reply | Quote

@NightOwl –

From the post that started this thread, 1868716, here’s the driver currently installed, listed at the very bottom of the long list of system specs/drivers:

Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Driver date: Thu 02/21/13
Driver version: 12.6.45.0

And, comparing that to your screenshot above, it looks as if @Morty ‘s already got the current driver for his NIC, so trying to get a new one might be a moot point.

1 user thanked author for this post.

Morty

Reply | Quote

I just ran devmgmt.msc and, under Network Adapters, Properties, Device description, I came up with this again:

Intel(R) 82579LM Gigabit Network Connection

But that doesn’t give me the name of a file to download and save for later, in case of emergency.

Under Location information, I got this:

PCI bus 0, device 25, function 0

Under Driver Details, it wouldn’t let me copy the info. Here’s a screenshot of what I got.

I still can’t figure out how to find and save the critical file to reinstall later, when we get off DEFCON2.

Thanks again!

Morty

Reply | Quote

I guess I have the same question as before. Should I download and save the file for later–after the next DEFCON all-clear?

Reply | Quote

@ Morty

Bob99 wrote:

From @mbhelwig ‘s post number 335959

To locate the network device, launch devmgmt.msc. It may appear under Other Devices.
1. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
2. Alternatively, install the drivers for the network device by right-clicking the device and choosing Update. Then choose Search automatically for updated driver software

or
Browse my computer for driver software (and install it–added by NightOwl).

For the record, my above posts allow you to do this particular step in Part 2 of how to recover if your Network Connection driver goes missing.

I have not discussed the above outline in detail yet, but that will have to wait until I return–just finishing packing right now.

1 user thanked author for this post.

Morty

Reply | Quote

anonymous wrote:

And, comparing that to your screenshot above, it looks as if @morty ‘s already got the current driver for his NIC, so trying to get a new one might be a moot point.

Thank you.

The plot thickens.

Now what?

Reply | Quote

Morty wrote:

The OS that Dell says it installed on your system was Win7 Ultimate, 32 bit. I think you have said in another thread somewhere (I can not remember where), that your system was a *refurbished* Dell system–is that true? Who *refurbished* it? And, does it have a tag of authentication for the OS? What does that tag say?

The refurb is from a private consultant who gets old office machines and refurbishes them. There’s a metal tag on the back and a sticker on top. Which is the authentication ticket?

I tried taking pictures of them, but couldn’t get a clear enough (legible) shot.

Reply | Quote

Hi Morty, anonymous 6536 here.

Last month in woody’s “MS-DEFCON 3: Get Windows XP, Win7 and associated Servers patched” forum you mentioned your DELL specs were:

Processor Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. A11, Fri 12/30/11
Name Intel(R) HD Graphics, Driver Version 9.17.10.3517
Network Adapter: Intel(R) 82579LM Gigabit Network Connection, Driver date: Thu 02/21/13, Driver version: 12.6.45.0

Also last month another anonymous posted this for you, “To locate the network device, launch devmgmt.msc (the Device Manager from Control panel as described in the other anonymous’ post just above this one); the network card may appear under Other Devices. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.” (This was related to kb4480970).
https://www.askwoody.com/forums/topic/ms-defcon-3-get-windows-xp-win7-and-associated-servers-patched/#post-1692108.

It may be you need to go into device Manager and tell it to re-scan for hardware and it will find it again.

However, if you want to get the newest Intel driver for that Network Card look at the drivers from the Intel Site:
https://downloadcenter.intel.com/product/47549/Intel-82579-Gigabit-Ethernet-Controller
Intel Network Adapter Driver for Windows 7 Version: 23.5.2 Date: 2/6/2019, 54.44 MB.

And a newer driver For Intel 82579LM Gigabit Ethernet PHY, Version: 24.1 (Latest) Date: 6/27/2019, 54.71 MB.
https://downloadcenter.intel.com/download/18713/Ethernet-Intel-Network-Adapter-Driver-for-Windows-7-?product=47620

Or look at what MS has to offer:

Windows Catalog:
Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection (64bit)
Windows 7,Windows Server 2008 R2, 11/12/2015 12.15.31.0 608 KB
https://www.catalog.update.microsoft.com/Search.aspx?q=82579LM

If you do not want to scan for changes after loosing the connection in Device Manager, aand you do not want to download and install a driver like NightOwl excellently portrayed with screenshots and arrows (well done NO) then you may have to consider joining Canadian Tech and go to Group W and cease updating. Depending on what happens with telemetry disabling or removal in the new June patches, I may have to join Group W too.

Morty keep us posted!

Edit: Correction: I meant the July Security Only patch KB4507456 just out.

1 user thanked author for this post.

Morty

Reply | Quote

anonymous wrote:

If you do not want to scan for changes after loosing the connection in Device Manager, aand you do not want to download and install a driver like NightOwl excellently portrayed with screenshots and arrows (well done NO) then you may have to consider joining Canadian Tech and go to Group W and cease updating. Depending on what happens with telemetry disabling or removal in the new June patches, I may have to join Group W too.

I basically replied to this above in #1875763.

The thing is that I can’t wait until after I lose connection to do this because then I can’t download a fix. I need to have a lifeboat ready before I sail.

Group W is not an option. I have to use the internet and I can’t go unprotected.

Thanks again, Morty

Reply | Quote

Hi Morty, anonymous 6536 here. I understand and agree. You need to download the drivers to your hard drive and research how to install them BEFORE you install the June or July patches.

Intel driver for that Network Card look at the drivers from the Intel Site:
Newest:
Intel 82579LM Gigabit Ethernet PHY, Version: 24.1 (Latest) Date: 6/27/2019, 54.71 MB.
https://downloadcenter.intel.com/download/18713/Ethernet-Intel-Network-Adapter-Driver-for-Windows-7-?product=47620

Older:
https://downloadcenter.intel.com/product/47549/Intel-82579-Gigabit-Ethernet-Controller
Intel Network Adapter Driver for Windows 7 Version: 23.5.2 Date: 2/6/2019, 54.44 MB.
(you may have to click “show more” to see the older releases).

Windows Catalog:
https://www.catalog.update.microsoft.com/Search.aspx?q=82579LM

Driver Model: Intel(R) 82579LM Gigabit Network Connection
Driver Provider: Intel
Version: 12.15.31.0
Version Date: 11/12/2015
Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection, Windows 7,Windows Server 2008 R2 (64bit)

Driver Manufacturer: Intel
Driver Class: Other Hardware
Driver Model: Intel(R) 82579LM Gigabit Network Connection
Driver Provider: Intel
Version: 12.15.31.0
Version Date: 11/12/2015
Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection, Windows 7 (x86, 32bit)

You need to download these drivers and put them into a folder for future use. Get all the drivers INCLUDING the current one you have from DELL support page as NightOwl showed.

Then after you get these, make a registry restore point or two for good measure. Install the June patch. If you loose your connection, then you have 4 network card drivers to try in case one fails. Lastly, you should be able to restore the registry and get back to square one. Should mind you.

Morty keep us posted!

1 user thanked author for this post.

Morty

Reply | Quote

[Morty]

anonymous wrote:

Morty keep us posted!

Bless you!

OK, here’s the latest:

I just downloaded these files from the Dell website:

Network_Driver_NNGMH_WN_18.1.0.0_A08.EXE
DIAG_Network_Intel_A09_x64-YMH42_setup_ZPE.exe

I’m going to file them away for now and wait for the next DEFCON all clear siren.

All the best to all of you, Morty

• This reply was modified 5 years, 8 months ago by Morty.

Reply | Quote

Hi Morty, If you want, Woody has already given the all clear for installation of the JUNE updates. We are waiting for the JULY updates to be approved. I do not know what I will do with July since they added telemetry to the SO updates. I will wait for Woody to give his opinion on that and any remedies to the telemetry issue.

6536

1 user thanked author for this post.

Morty

Reply | Quote

[Morty]

anonymous wrote:

I will wait for Woody to give his opinion on that and any remedies to the telemetry issue.

Thank you!

I backed up my files and ran the “Smart Backup” (whatever that does) on Easeus to update the full system backup I did last week. But it looks like I’m going to have to wait. The only “important” updates I’m being offered are these:

2019-07 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 and Server 2008 R2 for x64 (KB4507420)
2019-07 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4507449)
Windows Malicious Software Removal Tool x64 – July 2019 (KB890830)

• This reply was modified 5 years, 8 months ago by Morty.

Reply | Quote

Hi Morty, I think I understand. You must be using the windows update (WU) to get your updates and it is offering the new July cumulative update (Group A). Go to the below Microsoft Catalog page and get the 64 bit for you. Then you can manually install last months June patch.

2019-06 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4503292)
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4503292

However, if you would rather wait for July, that is OK but it may be another 3 weeks before we get the go ahead. If you are Group A, the telemetry does not matter. I am Group B and it does. If the telemetry does matter and you are Group A, then look into Spybot AntiBeacon. I believe 1.6 is still free since there is a 2.x and a 3.x being made.
https://www.safer-networking.org/anti-beacon-1-6-available/6536

1 user thanked author for this post.

Morty

Reply | Quote

Thanks again.

I’ve long given up on privacy. Between Microsoft and Google, they already know more about me than I do.

Now that you mention it, I remember reading about the update catalog. I’ll check it out. I guess I should have known better than coming in through the front door. Wish me luck! And Heaven help me.

Reply | Quote

OK, taking the plunge….

Reply | Quote

Private Morty reporting.

OK, I did the update from the catalog. As expected, it knocked out my network connection. So I installed

Network_Driver_NNGMH_WN_18.1.0.0_A08

And, thank Heaven, now it’s working again.

So now for the next question:

Do I also install

DIAG_Network_Intel_A09_x64-YMH42_setup_ZPE

or leave well enough alone?

Thanks again!

Reply | Quote

Hi Morty,

DIAG_Network_Intel_A09_x64-YMH42_setup_ZPE is a “Intel Device Manager Diagnostics Utility”. I don’t think you need that, especially if it is running OK. Keep it for a rainy day.

The Network_Driver_NNGMH_WN_18.1.0.0_A08 is the “Intel 825xx 10/100/1000 Ethernet Controller Driver” and it had; Version 18.1.0.0, A08, Release date 20 Jun 2013, Last Updated 11 Dec 2018. << something was added somewhere!

The only other items that may be worthy is a; BIOS update which is scary and dangerous to do or the “Intel Chipset Driver” that is a “driver” for the motherboard and should install just fine. But make a registry restore point for good measure.

Looks like you did it Morty! Good work! Now people will be coming to you for help!

6536

1 user thanked author for this post.

Morty

Reply | Quote

👏👍😎Yay! Congratulations, Morty, you did it! 😀

R/

Bob99

1 user thanked author for this post.

Morty

Reply | Quote

If it ain’t broke…

You have working solution, don’t tempt fate – unless you backup first.

cheers, Paul

1 user thanked author for this post.

Morty

Reply | Quote

Great advice. I’ve already got my back up over this. I’m not tempting fate. I’m on a low-fate diet.

Thank you; bless you.

Morty

Reply | Quote

anonymous wrote:

Looks like you did it Morty! Good work! Now people will be coming to you for help!

Ha! That’s all they and I need!

I’ll just send them to Woody and his Merry Persons. All for one and all for one!

I’m not starting up with anything I don’t have to. In the old days, I would spend hours tweaking my Autoexec.bat (remember those?). I don’t have as many hours now. As Paul T said, “If it ain’t broke, don’t fix it.”

Bless all of you!

 

Reply | Quote

Hah! Remember the Wild West days of tweaking autoexec.bat config.sys to get stuff to load into upper memory or into the 64K high memory area? I also used a utility called The Last Byte in order to get the most stuff to fit into the upper memory and high memory areas.

1 user thanked author for this post.

Morty

Reply | Quote

Morty wrote:

All for one and all for one!

Oops. Got that quote wrong. That wasn’t Robin Hood. It was the Three Musketeers.

Pick any heroes you like, you can add Woody and the Gang to the list.

Morty

Reply | Quote

anonymous wrote:

👏👍😎Yay! Congratulations, Morty, you did it! 😀

I didn’t do it. It was Woody’s Wonder Workers who did it.

Thank you all again!

Reply | Quote

@Morty –

Although you’ve successfully slain the figurative dragon this time, please save the network driver you downloaded from the Dell site in a safe place, as I suggested up in post #1872153. I have a feeling you’re going to need it in about 2½ weeks, when Woody will probably lower the MS-DEFCON setting to 3 or lower for us to install the July patches.

R/
Bob99

1 user thanked author for this post.

Morty

Reply | Quote

Bob99 wrote:

Although you’ve successfully slain the figurative dragon this time, please save the network driver you downloaded from the Dell site in a safe place, as I suggested up in post #1872153. I have a feeling you’re going to need it

“And hast thou slain the Jabberwock?

      Come to my arms, my beamish boy!

O frabjous day! Callooh! Callay!”

      He chortled in his joy.

I shall be sure to keep my vorpal sword in hand.

Many thanks!

Reply | Quote

GoneToPlaid wrote:

Hah! Remember the Wild West days of tweaking autoexec.bat config.sys

My upper and higher memory have faded along with Shane riding off into the sunset….

Reply | Quote