• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

Vista Hardware Driver Removal

V

VistaDJ

Well-known member
Joined
Dec 30, 2013
Posts
51
Hi All

New here so please bear with me.

I have Vista Service Pack 2 installed, this is on a HP Pavillion DV6000 Intel based system.

I have a problem with a hardware driver for an Intel LAN chip. I have tried doing an uninstall I have tried removing all the driver fragments in the registry I can find, however when trying to reinstall a driver to make the LAN Chip usable it will not install.

In Device Manager it shows under Network Adapters, Intel(R) PRO/1000 MT Mobile Connection with a yellow exclamation mark in front.

It also shows under Other devises, Ethernet Controller with a yellow exclamation mark in front.

I have tried doing an uninstall on both of these but both reapear in the same state.

I have tried several different registry cleaners.

I have tried a repair installation.

If trying to use the INTEL install package it reports no intel device found.

Is there any software available to track left over driver fragment or does any one have another suggestions.

Looking forward to any assistance or advise.

Oh a reinstall is out of the question at the moment.
 
VistaDJ said:
I have tried several different registry cleaners.
Click to expand...

Bad move!
Using such cleaners is as likely to make a problem worse, as better.

In Device Manager, click on View in the toolbar - select View Hidden Devices.
Are there any more devices with problems showing now?
How confident are you that the hardware itself is working?
 
Hi NoelDP

Firstly thank you very much for your reply.

The only reason I did try the reg cleaners was the reg was demaged anyway so took a punt I could do much more damage.

In Device Manager when showing Hidden Devices there is nothing extra displaying an error.

The hardware was working fine until this problem occured. I believe it was some Malware they screwed it up initially.

If it was a desktop I would just remove the card and then reinstall the drivers but as it is a Laptop that is not an option.
 
Thank you for the suggestion, however I have tried that trick. Both HP and Generic Intel drivers.

If I uninstall the Ethernet Controller that is shown under Other Devices it will automatically reinstall on the next reboot. So Vista can actually detect something there that requires drivers installed. However if I then stear the installer to the correct location of the drivers it can not install them.
 
I'm going to call for some more specialist assistance - in the meantime, please run an SFC scan..

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.


Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your reply - I can at least check that out :)
 
Hi,

The only reason I did try the reg cleaners was the reg was demaged anyway so took a punt I could do much more damage.
Click to expand...

Damaged in what way, were you receiving errors?

Regards,

Patrick
 
I suspect something is wrong with your Registry, and Registry Cleaners have made the situation even worse. Which Registry Cleaners did you run?
 
@ VistaDJ - can you run Windows System Restore using a restore point prior to the registry item(s) removal?
START | type rstrui

Is dv6000 the exact model number?

Have you tried HP support?
 
Hi NoelDP

Sorry for the delay in reply. ran the sfc /scannow tool as I have done many times before. Did not resolve the issue, I have however attached the log file for your perusal.

To answer your other option no a system restore is not an option.
 

Attachments

Patrick

It was damaged in the way that the driver for the LAN Adapter will not install. Yes Error code 1 and 31.
 
There is no SFC data in the CBS.log file :(
On the other hand, there are no obvious errors, either :)
Please copy the entire C:\Windows\logs\CBS folder to your desktop, zip it and upload it - if it's too large for the forum, delete the oldest of the CBSPersist files and try again.
 
NoelDP said:
There is no SFC data in the CBS.log file :(
On the other hand, there are no obvious errors, either :)
Please copy the entire C:\Windows\logs\CBS folder to your desktop, zip it and upload it - if it's too large for the forum, delete the oldest of the CBSPersist files and try again.
Click to expand...

Hi NoelDP

The previous file I sent you was an extract from the CBS.log file. It included every entry from the 1/1/2014.

To avoide any doubt I renamed the previous CBS.log file to .old and let SFC create a new log file when I reran it. The result of this is attached.
 

Attachments

NoelDP said:
There is no SFC data in the CBS.log file :(
On the other hand, there are no obvious errors, either :)
Please copy the entire C:\Windows\logs\CBS folder to your desktop, zip it and upload it - if it's too large for the forum, delete the oldest of the CBSPersist files and try again.
Click to expand...

Hi NoelDP

Just as a test and after reading an article and your comment about it may not be an Intel device if the Intel installer can not detect it I uninstalled the Intel(R) PRO/1000 MT Mobile Connection device and installed a Realtek RTL8139/810x Family Fast Ethernet NIC. This however installed the same way as the Intel LAN Adapter and the Ethernet Controller installed just the same as previous. After this I performed a Devcon Find Device report for you to show how the two devices are installed. The Realtek RTL8139/810x Family Fast Ethernet NIC or Intel(R) PRO/1000 MT Mobile Connection are installed under ROOT\NET\0000 and the Ethernet Controller installed under PCI\VEN_8086&DEV_1000&SUBSYS_30BB0004&REV_00\4&2CA88C27&2&00E2:.

This leads to another interesting observation in Device Manager the two Devices have two different Hardware ID's. The device Realtek RTL8139/810x Family Fast Ethernet NIC displays an Intel LAN Adapter hardware ID and the device Ethernet Controller displays a Realtek RTL8139/810x Family Fast Ethernet NIC.

Screen shot of Devcon Report and device properties attached.
 

Attachments

The CBS log now gives us some real data to work with :)
Code: 
 Line 3046: 2014-01-02 12:08:49, Info                  CSI    000001da [SR] Repairing 2 components
 Line 3047: 2014-01-02 12:08:49, Info                  CSI    000001db [SR] Beginning Verify and Repair transaction
 Line 3048: 2014-01-02 12:08:49, Info                  CSI    000001dc [SR] Cannot repair member file [l:22{11}]"MsMpRes.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3049: 2014-01-02 12:08:49, Info                  CSI    000001dd [SR] Cannot repair member file [l:24{12}]"MpClient.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3050: 2014-01-02 12:08:49, Info                  CSI    000001de [SR] Cannot repair member file [l:24{12}]"MpCmdRun.exe" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3051: 2014-01-02 12:08:49, Info                  CSI    000001df [SR] Cannot repair member file [l:24{12}]"MpAsDesc.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3052: 2014-01-02 12:08:49, Info                  CSI    000001e0 [SR] Cannot repair member file [l:18{9}]"MpSvc.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3053: 2014-01-02 12:08:49, Info                  CSI    000001e1 [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3054: 2014-01-02 12:08:49, Info                  CSI    000001e2 [SR] Cannot repair member file [l:24{12}]"MsMpLics.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3055: 2014-01-02 12:08:49, Info                  CSI    000001e3 [SR] Cannot repair member file [l:22{11}]"MSASCui.exe" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3056: 2014-01-02 12:08:49, Info                  CSI    000001e4 [SR] Cannot repair member file [l:22{11}]"MpRtMon.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3057: 2014-01-02 12:08:49, Info                  CSI    000001e5 [SR] Cannot repair member file [l:24{12}]"MpRtPlug.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3058: 2014-01-02 12:08:49, Info                  CSI    000001e6 [SR] Cannot repair member file [l:24{12}]"MpSigDwn.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3059: 2014-01-02 12:08:49, Info                  CSI    000001e7 [SR] Cannot repair member file [l:24{12}]"MpSoftEx.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3060: 2014-01-02 12:08:49, Info                  CSI    000001e8 [SR] Cannot repair member file [l:18{9}]"MpOAV.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3061: 2014-01-02 12:08:49, Info                  CSI    000001e9 [SR] Cannot repair member file [l:22{11}]"MpEvMsg.dll" of Security-Malware-Windows-Defender-Events, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing


Somebody/thing has ripped Defender out by the roots, and left a mess behind :(

I've never seen this pattern before, but it's obviously by deliberate action of some kind - any idea whose?
What Anti-Virus/Malware programs have EVER been installed on this machine?

I have no idea how this could impact on the actual problem you're complaining of, but we'd best fix it.
I'll post the protocol a bit later.
 
I've uploaded a file - vdlaa.zip - to my SkyDrive at Noel's SkyDrive

Please download and save it.


Right-click on the saved file and select Extract all...

Change the target to C:\ and click on Extract

Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start
tapping F8 - this should bring up the Advanced Boot Menu, at the top of which
should be the option 'Repair my Computer'

Pick that

You'll have to log in with your username and password.


Pick the option to use a Command Prompt

At the prompt type

DIR C:\vdlaa

hit the enter key - if you get a 'Not
Found' error try

DIR D:\vdlaa

or

DIR E:\vdlaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\vdlaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.


Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot and upload the new CBS.log file to your reply


Also run a new MGADiag report, and post the result.
 
Last edited:
Here's the summary/..
Code: 
 Line 4992: 2014-01-02 23:33:45, Info                  CSI    000001b0 [SR] Repairing 0 components
 Line 4993: 2014-01-02 23:33:45, Info                  CSI    000001b1 [SR] Beginning Verify and Repair transaction
 Line 4998: 2014-01-02 23:33:45, Info                  CSI    000001b3 [SR] Repair complete

... so it appears to have worked properly :)

Now please download and save the CheckSUR tool from Use System Update Readiness tool to fix package corruption errors
(you'll need to look in the details for Vista, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top