If this is the case then we need to let them finish what they are doing as anything we do could potentially be a problem with them and vice versa.
after trojan removal, speakers, internet, printer don't work
Started by
mjcy
, Apr 27 2009 10:28 PM
#16
Posted 05 May 2009 - 08:54 AM
If this is the case then we need to let them finish what they are doing as anything we do could potentially be a problem with them and vice versa.
#17
Posted 05 May 2009 - 05:24 PM
Yea, this might be malware related. Since you had the blue screen after installing the sound driver, try rolling it back, so that malware removal can be easier.
#18
Posted 05 May 2009 - 05:48 PM
the malware guys will probably have you do this but you also need to get SP2 and the 80 + updates to it or you will continue to get infected...thats what most of the updates do is patch the system so you can't get infected...example: last Octobers update patched against the conflicter worm...
#19
Posted 06 May 2009 - 05:18 AM
This doesn't seem to be malware related, we are about to finish up with him, so feel free to keep your suggestions going
#20
Posted 06 May 2009 - 05:56 AM
got it...
#21
Posted 06 May 2009 - 08:50 AM
Hi, thanks for all the suggestions...!
BSOD is gone now for some reason... I turned on the computer again to try to access a file, and it never BSOD'd. So maybe it just needed a couple of reboots to get the sound all sorted??
Anyway, I will finish on the Malware thread and be back.
BSOD is gone now for some reason... I turned on the computer again to try to access a file, and it never BSOD'd. So maybe it just needed a couple of reboots to get the sound all sorted??
Anyway, I will finish on the Malware thread and be back.
#22
Posted 06 May 2009 - 08:53 AM
once your cleared by the malware pros...go to windows update and get ALL the critical updates at least...
#23
Posted 06 May 2009 - 08:55 AM
happyrock: Thanks, but please read my first post. I can't get Windows to update. That is one of my major problems that still exists.
#24
Posted 06 May 2009 - 09:01 AM
AFTER YOUR DONE with the malware guys...
try this
Download WUFix.exe to your desktop.
Double-Click WUFix.exe to run fix.
You will see a window open and commands processing. When the window closes the fix will have completed.
Restart the computer.
This fix will clear the proxy cache, places Windows Update sites in the Trusted Zone, places Windows Update sites in the exception list of IE Popup Blocker, starts all dependent services, registers required DLLS, empties the Windows Update temporary folder (with backup), renames the catroot2 folder, retains update history and Event log, and deletes BITS pending download queue.
go here...
nojoy ...
then a repair is in order...go here for the how to guide...
try this
Download WUFix.exe to your desktop.
Double-Click WUFix.exe to run fix.
You will see a window open and commands processing. When the window closes the fix will have completed.
Restart the computer.
This fix will clear the proxy cache, places Windows Update sites in the Trusted Zone, places Windows Update sites in the exception list of IE Popup Blocker, starts all dependent services, registers required DLLS, empties the Windows Update temporary folder (with backup), renames the catroot2 folder, retains update history and Event log, and deletes BITS pending download queue.
go here...
nojoy ...
then a repair is in order...go here for the how to guide...
#25
Posted 06 May 2009 - 04:09 PM
Whew!
Okay, the Malware area has declared me clean.
I ran the windows update fix; it failed to run step one but did run all the rest. I rebooted and tried to run windows update, same problem. It said:
We've made improvements to our website. To download the new version of the software and begin using Windows Update, please click Install Now.
When I clicked Install Now, it went through to 100% downloaded and 100% registered and then said:
The website has encountered a problem and cannot display the page you are trying to view. The options provided below might help you solve the problem. [Error number: 0x8024D007]
When I went to their "find solutions" option and searched the error number, they produced no results.
I did the repair from boot disk just before I started on this forum... when my desktop was blank. It didn't fix Windows Update then... should I really do that again now? Not to argue with your advice; I just feel like I'm going back to square one.
Okay, the Malware area has declared me clean.
I ran the windows update fix; it failed to run step one but did run all the rest. I rebooted and tried to run windows update, same problem. It said:
We've made improvements to our website. To download the new version of the software and begin using Windows Update, please click Install Now.
When I clicked Install Now, it went through to 100% downloaded and 100% registered and then said:
The website has encountered a problem and cannot display the page you are trying to view. The options provided below might help you solve the problem. [Error number: 0x8024D007]
When I went to their "find solutions" option and searched the error number, they produced no results.
I did the repair from boot disk just before I started on this forum... when my desktop was blank. It didn't fix Windows Update then... should I really do that again now? Not to argue with your advice; I just feel like I'm going back to square one.
#26
Posted 06 May 2009 - 05:05 PM
ok.... try Dial-a-fix 0.60.0.24...get it here...
Dial-a-fix is a collection of 'known fixes' that have been compiled over the past year that really knock out some serious Windows problems, all with one or two clicks. "When in doubt, check 'em all".Dial-a-fix tackles issues with SSL/Cryptography, Windows Update, Microsoft Installer, and many miscellaneous shell problems. Example: If you get a blank screen when trying to visit Windows update... [read more at the download site
Error number: 0x8024D007
This error is in part a failure of the machine to validate that it is a
genuine product from microsoft. You can download the executable onto your
local desktop and run it manually.
Dial-a-fix is a collection of 'known fixes' that have been compiled over the past year that really knock out some serious Windows problems, all with one or two clicks. "When in doubt, check 'em all".Dial-a-fix tackles issues with SSL/Cryptography, Windows Update, Microsoft Installer, and many miscellaneous shell problems. Example: If you get a blank screen when trying to visit Windows update... [read more at the download site
Error number: 0x8024D007
This error is in part a failure of the machine to validate that it is a
genuine product from microsoft. You can download the executable onto your
local desktop and run it manually.
Edited by happyrock, 06 May 2009 - 05:35 PM.
#27
Posted 06 May 2009 - 05:07 PM
Does your sound and printer still work? I'm not so sure on what to do about the Windows Update problem, so happyrock can address that when he returns.
Now for the network connection problem. Go to Start -> Run -> services.msc
Scroll down to Wireless Zero Configuration, and tell me if that service is started or not.
Some wireless connection software that comes with laptops may not show you all networks available due to security settings or prompts you may have answered in the past. In this case it is better to let Windows manage wireless connections instead of the adapter's software.
In Windows XP you right click on the Windows wireless adapter Icon by the clock and choose Status from the menu and then click on the Properties button in the status window.
In Windows Vista right click on the Windows wireless adapter Icon by the clock and choose "Network and sharing center" and in the Tasks Pane click on "Manage Network Connections".
You should see your wireless adapter in the list of connections. (If it is not there it is defective or not properly installed.)
Right click on your wireless adapter and choose properties.
At the top of the Wireless Connections tab select the check box that says "Use windows to manage my wireless connections"
Now for the network connection problem. Go to Start -> Run -> services.msc
Scroll down to Wireless Zero Configuration, and tell me if that service is started or not.
Some wireless connection software that comes with laptops may not show you all networks available due to security settings or prompts you may have answered in the past. In this case it is better to let Windows manage wireless connections instead of the adapter's software.
In Windows XP you right click on the Windows wireless adapter Icon by the clock and choose Status from the menu and then click on the Properties button in the status window.
In Windows Vista right click on the Windows wireless adapter Icon by the clock and choose "Network and sharing center" and in the Tasks Pane click on "Manage Network Connections".
You should see your wireless adapter in the list of connections. (If it is not there it is defective or not properly installed.)
Right click on your wireless adapter and choose properties.
At the top of the Wireless Connections tab select the check box that says "Use windows to manage my wireless connections"
#28
Posted 08 May 2009 - 10:26 AM
Please Go to
1: STARTand the click on RUN
2: Type in devmgmt.msc
3: Click Enter
4. Look for any entries with Yellow Exclamation marks or Red X's
In your next reply please iclude those results
1: STARTand the click on RUN
2: Type in devmgmt.msc
3: Click Enter
4. Look for any entries with Yellow Exclamation marks or Red X's
In your next reply please iclude those results
#29
Posted 08 May 2009 - 10:31 AM
happyrock: Tried Dial-a-fix. Checked everything. It gave me 3 error messages when trying to fix windows update. Here is the log:
--- Windows Update ---
--- Registration: Windows Update/Automatic Update DLLs ---
7:28:48 PM | Unregistered: C:\WINDOWS\system32\msxml.dll
7:28:48 PM | Registered: C:\WINDOWS\system32\msxml.dll
7:28:48 PM | Unregistered: C:\WINDOWS\system32\msxml2.dll
7:28:48 PM | Registered: C:\WINDOWS\system32\msxml2.dll
7:28:48 PM | Unregistered: C:\WINDOWS\system32\msxml3.dll
7:28:49 PM | Registered: C:\WINDOWS\system32\msxml3.dll
7:28:49 PM | Error 127: C:\WINDOWS\system32\qmgr.dll is not unregisterable or the file is corrupted. Version: 6.2.2600.1106
7:28:53 PM | Error 127: C:\WINDOWS\system32\qmgr.dll is not registerable or the file is corrupted. Version: 6.2.2600.1106
7:28:54 PM | Unregistered: C:\WINDOWS\system32\qmgrprxy.dll
7:28:54 PM | Registered: C:\WINDOWS\system32\qmgrprxy.dll
7:28:54 PM | Unregistered: C:\WINDOWS\system32\muweb.dll
7:28:54 PM | Registered: C:\WINDOWS\system32\muweb.dll
7:28:54 PM | Unregistered: C:\WINDOWS\system32\winhttp.dll
7:28:54 PM | Registered: C:\WINDOWS\system32\winhttp.dll
7:28:55 PM | Registered: C:\WINDOWS\system32\wuapi.dll
7:28:55 PM | Unregistered: C:\WINDOWS\system32\wuaueng.dll
7:29:02 PM | Error during registration of C:\WINDOWS\system32\wuaueng.dll - version: 5.4.3630.1106. The error returned is: Unspecified error
(-2147467259)
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wuaueng1.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wuaueng1.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wucltui.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wucltui.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wups.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wups.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wups2.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wups2.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wuweb.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wuweb.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\ole32.dll
--- SSL/HTTPS/Cryptography ---
7:29:03 PM | Executed 'cmd.exe /c rmdir /q /s C:\WINDOWS\System32\Catroot2'
--- Registration: SSL/HTTPS/Cryptography ---
7:29:03 PM | Unregistered: C:\WINDOWS\system32\cryptdlg.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\cryptdlg.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\cryptui.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\cryptui.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\cryptext.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\cryptext.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\dssenh.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\dssenh.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\gpkcsp.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\gpkcsp.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\initpki.dll
7:29:12 PM | Registered: C:\WINDOWS\system32\initpki.dll
7:29:12 PM | Unregistered: C:\WINDOWS\system32\licdll.dll
7:29:12 PM | Registered: C:\WINDOWS\system32\licdll.dll
7:29:12 PM | Unregistered: C:\WINDOWS\system32\mssign32.dll
7:29:12 PM | Registered: C:\WINDOWS\system32\mssign32.dll
7:29:12 PM | Unregistered: C:\WINDOWS\system32\mssip32.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\mssip32.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\scardssp.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\scardssp.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\sccbase.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\sccbase.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\scecli.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\scecli.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\softpub.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\softpub.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\slbcsp.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\slbcsp.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\regwizc.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\regwizc.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\rsaenh.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\rsaenh.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\winhttp.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\winhttp.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\wintrust.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\wintrust.dll
--- Registration: Programming cores/runtimes ---
7:29:14 PM | Registered: C:\WINDOWS\system32\atl.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\corpol.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\jscript.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\dispex.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\scrrun.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\scrobj.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\vbscript.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\wshext.dll
---
Also downloaded WindowsXP-KB835935-SP2-ENU.exe from Microsoft support site to do manual install of SP2, but it got hung up about 1/4 of the way through the install, on "Running Processes Before Installing." I let it run for a few hours, and it never made it past that point.
---
Edge2022: In Wireless Connection Properties (right-clicked on Wireless Adapter, selected Status, then Properties), I see this:
Connect Using:
D-Link WDA-2320 Desktop Adapter (that is my wireless adapter)
This connection uses the following items (all are checked):
- Client for Microsoft Networks
- File and Printer Sharing for Microsoft Networks
- QoS Packet Scheduler
- Internet Protocol (TCP/IP)
I don't have a network -- don't know if that matters here. My ethernet thingy is not on this list, nor is my wireless adapter.
Not sure where you mean for me to right-click the wireless adapter and choose properties... In the system tray, no "properties" option available; in the Wireless adapter properties dialog, no right click available on listing under "Connect using..."
Should I try reinstalling the driver for the wireless adapter?
--- Windows Update ---
--- Registration: Windows Update/Automatic Update DLLs ---
7:28:48 PM | Unregistered: C:\WINDOWS\system32\msxml.dll
7:28:48 PM | Registered: C:\WINDOWS\system32\msxml.dll
7:28:48 PM | Unregistered: C:\WINDOWS\system32\msxml2.dll
7:28:48 PM | Registered: C:\WINDOWS\system32\msxml2.dll
7:28:48 PM | Unregistered: C:\WINDOWS\system32\msxml3.dll
7:28:49 PM | Registered: C:\WINDOWS\system32\msxml3.dll
7:28:49 PM | Error 127: C:\WINDOWS\system32\qmgr.dll is not unregisterable or the file is corrupted. Version: 6.2.2600.1106
7:28:53 PM | Error 127: C:\WINDOWS\system32\qmgr.dll is not registerable or the file is corrupted. Version: 6.2.2600.1106
7:28:54 PM | Unregistered: C:\WINDOWS\system32\qmgrprxy.dll
7:28:54 PM | Registered: C:\WINDOWS\system32\qmgrprxy.dll
7:28:54 PM | Unregistered: C:\WINDOWS\system32\muweb.dll
7:28:54 PM | Registered: C:\WINDOWS\system32\muweb.dll
7:28:54 PM | Unregistered: C:\WINDOWS\system32\winhttp.dll
7:28:54 PM | Registered: C:\WINDOWS\system32\winhttp.dll
7:28:55 PM | Registered: C:\WINDOWS\system32\wuapi.dll
7:28:55 PM | Unregistered: C:\WINDOWS\system32\wuaueng.dll
7:29:02 PM | Error during registration of C:\WINDOWS\system32\wuaueng.dll - version: 5.4.3630.1106. The error returned is: Unspecified error
(-2147467259)
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wuaueng1.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wuaueng1.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wucltui.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wucltui.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wups.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wups.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wups2.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wups2.dll
7:29:02 PM | Unregistered: C:\WINDOWS\system32\wuweb.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\wuweb.dll
7:29:02 PM | Registered: C:\WINDOWS\system32\ole32.dll
--- SSL/HTTPS/Cryptography ---
7:29:03 PM | Executed 'cmd.exe /c rmdir /q /s C:\WINDOWS\System32\Catroot2'
--- Registration: SSL/HTTPS/Cryptography ---
7:29:03 PM | Unregistered: C:\WINDOWS\system32\cryptdlg.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\cryptdlg.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\cryptui.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\cryptui.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\cryptext.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\cryptext.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\dssenh.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\dssenh.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\gpkcsp.dll
7:29:03 PM | Registered: C:\WINDOWS\system32\gpkcsp.dll
7:29:03 PM | Unregistered: C:\WINDOWS\system32\initpki.dll
7:29:12 PM | Registered: C:\WINDOWS\system32\initpki.dll
7:29:12 PM | Unregistered: C:\WINDOWS\system32\licdll.dll
7:29:12 PM | Registered: C:\WINDOWS\system32\licdll.dll
7:29:12 PM | Unregistered: C:\WINDOWS\system32\mssign32.dll
7:29:12 PM | Registered: C:\WINDOWS\system32\mssign32.dll
7:29:12 PM | Unregistered: C:\WINDOWS\system32\mssip32.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\mssip32.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\scardssp.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\scardssp.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\sccbase.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\sccbase.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\scecli.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\scecli.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\softpub.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\softpub.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\slbcsp.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\slbcsp.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\regwizc.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\regwizc.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\rsaenh.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\rsaenh.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\winhttp.dll
7:29:13 PM | Registered: C:\WINDOWS\system32\winhttp.dll
7:29:13 PM | Unregistered: C:\WINDOWS\system32\wintrust.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\wintrust.dll
--- Registration: Programming cores/runtimes ---
7:29:14 PM | Registered: C:\WINDOWS\system32\atl.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\corpol.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\jscript.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\dispex.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\scrrun.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\scrobj.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\vbscript.dll
7:29:14 PM | Registered: C:\WINDOWS\system32\wshext.dll
---
Also downloaded WindowsXP-KB835935-SP2-ENU.exe from Microsoft support site to do manual install of SP2, but it got hung up about 1/4 of the way through the install, on "Running Processes Before Installing." I let it run for a few hours, and it never made it past that point.
---
Edge2022: In Wireless Connection Properties (right-clicked on Wireless Adapter, selected Status, then Properties), I see this:
Connect Using:
D-Link WDA-2320 Desktop Adapter (that is my wireless adapter)
This connection uses the following items (all are checked):
- Client for Microsoft Networks
- File and Printer Sharing for Microsoft Networks
- QoS Packet Scheduler
- Internet Protocol (TCP/IP)
I don't have a network -- don't know if that matters here. My ethernet thingy is not on this list, nor is my wireless adapter.
Not sure where you mean for me to right-click the wireless adapter and choose properties... In the system tray, no "properties" option available; in the Wireless adapter properties dialog, no right click available on listing under "Connect using..."
Should I try reinstalling the driver for the wireless adapter?
#30
Posted 08 May 2009 - 10:34 AM
rshaffer: no red x's or yellow exclamation points.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users