Password reset and notification emails are now sending correctly.
If you recently requested a password reset, please check your inbox (and spam folder just in case).
You can now reset your password and log in as normal.
Welcome back to PCHF, and thank you for your patience during our migration process!
— The PCHF Team
Welcome to PC Help Forum!
You’re viewing our community as a guest.
That means you can browse posts, but can’t yet reply or start new topics.
Join us today — it's completely free!
As a member, you'll be able to:
✅ Get personalized tech support from trusted volunteers
🦠 Work one-on-one with our Malware Removal Specialists
Have deleted instances of TechUtilities using “Everything”.
I am running the latest version of CCleaner (V5.38)
Still no change
What do you advise for the next step?
We need a security expert to take a look at this, being the Christmas period there may be some delay but as the program got on your computer without you knowing and you all of a sudden have this issue the program could be involved, meanwhile can you do the following;
Download/run then post an Autoruns log for us, free to download from here
1: Extract the Autoruns Zip file contents to a folder.
2: Double-click the “Autoruns.exe”.
3: Click on the "Hide Signed Microsoft and Windows Entries” option.
4: Go to File then to Export As or Save in some versions.
5: Save AutoRuns.txt file to known location like your Desktop > when you click on File > Save you will then get the option to Save as type, click the drop down tab, change it to Text and then click the Save button.
Quick question or two, you have BitDefender Anti Virus/Malware protecting your computer, do you have a link to the Zemana AntiMalware software showing up in AutoRuns.
Have you checked the Device Manager for any yellow ! or red Xs against your drives.
Lets see how the drives show up in Disk Manager;
Click on the Start button and then choose Control Panel.
Click on the System and Security link.
Note: If you’re viewing the Large icons or Small iconsview of Control Panel, you won’t see this link so just click on the Administrative Tools icon and skip to Step 4.
In the System and Security window, click on the Administrative Tools heading located near the bottom of the window.
In the Administrative Tools window, double-click on the Computer Management icon.
When Computer Management opens, click on Disk Management on the left side of the window, located under Storage.
After a brief loading period, Disk Management should now appear on the right side of the Computer Management window.
Note: If you don’t see Disk Management listed, you may need to click on the |> icon to the left of the Storage icon.
To capture and post a screenshot;
Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start…all programs…accessories…paint…left click in the white area …press CTRL + V…click on file…click on save…save it to your desktop…name it something related to the screen your capturing… BE SURE TO SAVE IT AS A .JPG …otherwise it may be to big to upload… then after typing in any response you have… click on the Upload a File tab.
Thanks Roger, the Zemana is not the full real time protection package then, you would be amazed at the amount of people that have been caught out by the free 14 day trial of Malwarebytes which offers full real time protection for 14 days before going back to the basic on demand scanner if not paid for to permanently upgrade.
Originally posted by roger hawke
. phil’ - not sure what you mean??
No problem, covered above but just to confirm was checking to make sure that the Zemana was not the full AV package.
This is definitely not hardware related, I suspect that it is registry related and something potentially caused by the rogue TechUtilities garbage that got on your machine somehow.
Need to wait on some malware expertise for now I`m afraid.
As a precaution, if you happen to use USB thumb drives or external HDDs, please do not connect them to this computer until you have been given the all clear of malware on it.
Hi Phill and Roger, recently whilst cleaning Rogers PC I recommended he use Bitdefender as his realtime security. We also ran a scan with Zemana and I suggested he keep it as a second opinion/run as required scanner. Yes Zemana only runs as realtime for 14 days, and yes whilst it is not desirable to run more than one realtime security app at the same time it was only for the two weeks till Zemana reverted to manual scan only.
With Bitdefender running realtime and Zemana as required should give Roger excellent ongoing protection?
If you receive any security warnings, or the User Account Control warning opens at any time whilst using FRST you can safely allow FRST to proceed.
Frst will open with two dialogue boxes, accept the disclaimer.
[ol]
[li]Accept the default whitelist options,[/li][li]If the additions.txt options box is not checked please select it. [/li]
[li]Then select “Scan”[/li][/ol]
Frst will take a few minutes to scan your computer, and when finished will produce two log files on your desktop, FRST.txt, and Addition.txt. They will display immediately on the desktop, but can be reopened later as a notepad file.
Please COPY and PASTE the contents of these two files in your next post.
We will need a log from AdwCleaner for further information.
Please download a copy of AdwCleaner from HERE, it is important to download it to your desktop.
Once downloaded to the desktop AdwCleaner will create an icon [MEDIA=imgur]eEGkHPS[/MEDIA]
Should you receive any security warnings or your User Account Control warning appears whilst you are using this application you can safely allow AdwCleaner to continue.
Before running AdwCleaner please ensure all other programs and browsers are closed, then double left click the icon to open it.
AdwCleaner will open, click the scan button to start searching.
[MEDIA=imgur]hBYSf6z[/MEDIA]
The scan may take some time to complete, and when it has any malware found will be automatically selected for quarantining. Click the “Clean” button.
[MEDIA=imgur]ftC2WaB[/MEDIA]
After a few seconds a message should tell you your computer will now reboot. Allow the reboot.
When the computer restarts a log file will be displayed, but if its closed for any reason before copying the contents, you will find a copy of the file if you navigate to C:\AdwCleaner[C#].txt (The C denotes the Cleaning log)
[MEDIA=imgur]jr9Bx9h[/MEDIA]
Please Copy and Paste the contents of the log file with your next reply.
Roger, please copy and paste any logs, as per instructions. I have pasted the current ones.
Scan result of Farbar Recovery Scan Tool (FRST) (x64) Version: 26-12-2017
Ran by Roger (administrator) on ROGER-PC (27-12-2017 08:49:52)
Running from C:\Users\Roger\Desktop
Loaded Profiles: Roger (Available Profiles: Roger)
Platform: Windows 7 Professional Service Pack 1 (X64) Language: English (United States)
Internet Explorer Version 11 (Default browser: IE)
Boot Mode: Normal
Tutorial for Farbar Recovery Scan Tool: http://www.geekstogo.com/forum/topic...ery-scan-tool/
(There is no automatic fix for files that do not pass verification.)
C:\Windows\system32\winlogon.exe => File is digitally signed
C:\Windows\system32\wininit.exe => File is digitally signed
C:\Windows\SysWOW64\wininit.exe => File is digitally signed
C:\Windows\explorer.exe => File is digitally signed
C:\Windows\SysWOW64\explorer.exe => File is digitally signed
C:\Windows\system32\svchost.exe => File is digitally signed
C:\Windows\SysWOW64\svchost.exe => File is digitally signed
C:\Windows\system32\services.exe => File is digitally signed
C:\Windows\system32\User32.dll => File is digitally signed
C:\Windows\SysWOW64\User32.dll => File is digitally signed
C:\Windows\system32\userinit.exe => File is digitally signed
C:\Windows\SysWOW64\userinit.exe => File is digitally signed
C:\Windows\system32\rpcss.dll => File is digitally signed
C:\Windows\system32\dnsapi.dll => File is digitally signed
C:\Windows\SysWOW64\dnsapi.dll => File is digitally signed
C:\Windows\system32\Drivers\volsnap.sys => File is digitally signed
LastRegBack: 2017-12-20 10:59
==================== End of FRST.txt ============================
[HEADING=1]Additional scan result of Farbar Recovery Scan Tool (x64) Version: 26-12-2017
Ran by Roger (27-12-2017 08:52:04)
Running from C:\Users\Roger\Desktop
Windows 7 Professional Service Pack 1 (X64) (2013-03-20 15:21:36)
Boot Mode: Normal[/HEADING]
==================== Accounts: =============================
==================== Security Center ========================
(If an entry is included in the fixlist, it will be removed.)
AV: Bitdefender Antivirus Free Antimalware (Enabled - Up to date) {3FB17364-4FCC-0FA7-6BBF-973897395371}
AS: Bitdefender Antivirus Free Antimalware (Enabled - Up to date) {84D09280-69F6-0029-510F-AC4AECBE19CC}
AS: Windows Defender (Disabled - Out of date) {D68DDC3A-831F-4fae-9E44-DA132C1ACF46}
Name: Microsoft PS/2 Mouse
Description: Microsoft PS/2 Mouse
Class Guid: {4d36e96f-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: i8042prt
Problem: : This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)
Resolution: The device is installed incorrectly. The problem could be a hardware failure, or a new driver might be needed.
Devices stay in this state if they have been prepared for removal.
After you remove the device, this error disappears.Remove the device, and this error should be resolved.
Name: Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.20)
Description: Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.20)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Realtek
Service: RTL8167
Problem: : This device is disabled. (Code 22)
Resolution: In Device Manager, click “Action”, and then click “Enable Device”. This starts the Enable Device wizard. Follow the instructions.
Name: Standard PS/2 Keyboard
Description: Standard PS/2 Keyboard
Class Guid: {4d36e96b-e325-11ce-bfc1-08002be10318}
Manufacturer: (Standard keyboards)
Service: i8042prt
Problem: : This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)
Resolution: The device is installed incorrectly. The problem could be a hardware failure, or a new driver might be needed.
Devices stay in this state if they have been prepared for removal.
After you remove the device, this error disappears.Remove the device, and this error should be resolved.
==================== Event log errors: =========================
[HEADING=1]Application errors:[/HEADING]
Error: (12/27/2017 08:44:48 AM) (Source: Windows Search Service) (EventID: 7010) (User: )
Description: The index cannot be initialized.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Error: (12/27/2017 08:44:48 AM) (Source: Windows Search Service) (EventID: 3058) (User: )
Description: The application cannot be initialized.
Context: Windows Application
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Error: (12/27/2017 08:44:48 AM) (Source: Windows Search Service) (EventID: 3028) (User: )
Description: The gatherer object cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Error: (12/27/2017 08:44:48 AM) (Source: Windows Search Service) (EventID: 3029) (User: )
Description: The plug-in in <Search.TripoliIndexer> cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
Element not found. (HRESULT : 0x80070490) (0x80070490)
Error: (12/27/2017 08:44:44 AM) (Source: Windows Search Service) (EventID: 3029) (User: )
Description: The plug-in in <Search.JetPropStore> cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Error: (12/27/2017 08:44:44 AM) (Source: Windows Search Service) (EventID: 9002) (User: )
Description: The Windows Search Service cannot load the property store information.
Context: Windows Application, SystemIndex Catalog
Details:
The content index database is corrupt. (HRESULT : 0xc0041800) (0xc0041800)
Error: (12/27/2017 08:44:44 AM) (Source: Windows Search Service) (EventID: 7042) (User: )
Description: The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Error: (12/27/2017 08:44:44 AM) (Source: Windows Search Service) (EventID: 7040) (User: )
Description: The search service has detected corrupted data files in the index {id=4700}. The service will attempt to automatically correct this problem by rebuilding the index.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
Error: (12/27/2017 08:44:44 AM) (Source: Windows Search Service) (EventID: 9000) (User: )
Description: The Windows Search Service cannot open the Jet property store.
Details:
0x%08x (0xc0041800 - The content index database is corrupt. (HRESULT : 0xc0041800))
Error: (12/27/2017 08:44:44 AM) (Source: ESENT) (EventID: 455) (User: )
Description: Windows (2548) Windows: Error -1811 occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\MSS0040A.log.
[HEADING=1]System errors:[/HEADING]
Error: (12/27/2017 08:45:32 AM) (Source: Service Control Manager) (EventID: 7001) (User: )
Description: The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error:
%%-2140993535
Error: (12/27/2017 08:45:32 AM) (Source: Service Control Manager) (EventID: 7023) (User: )
Description: The Peer Name Resolution Protocol service terminated with the following error:
%%-2140993535
Error: (12/27/2017 08:45:32 AM) (Source: Service Control Manager) (EventID: 7001) (User: )
Description: The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error:
%%-2140993535
Error: (12/27/2017 08:45:32 AM) (Source: Service Control Manager) (EventID: 7023) (User: )
Description: The Peer Name Resolution Protocol service terminated with the following error:
%%-2140993535
Error: (12/27/2017 08:45:32 AM) (Source: PNRPSvc) (EventID: 102) (User: )
Description: The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630801.
Error: (12/27/2017 08:45:32 AM) (Source: PNRPSvc) (EventID: 102) (User: )
Description: The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630801.
Error: (12/27/2017 08:45:22 AM) (Source: Service Control Manager) (EventID: 7001) (User: )
Description: The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error:
%%-2140993535
Error: (12/27/2017 08:45:22 AM) (Source: Service Control Manager) (EventID: 7023) (User: )
Description: The Peer Name Resolution Protocol service terminated with the following error:
%%-2140993535
Error: (12/27/2017 08:45:22 AM) (Source: PNRPSvc) (EventID: 102) (User: )
Description: The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630801.
Error: (12/27/2017 08:45:12 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
Description: The Windows Search service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
[HEADING=1]CodeIntegrity:[/HEADING]
Date: 2016-10-30 20:30:12.143
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\P EAuth.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
Date: 2016-10-30 20:30:12.096
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\P EAuth.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
Date: 2016-10-30 20:30:05.747
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\audiodg.e xe because the set of per-page image hashes could not be found on the system.
Date: 2016-10-30 20:18:16.704
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\audiodg.e xe because the set of per-page image hashes could not be found on the system.
Date: 2016-10-30 16:39:11.283
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\P EAuth.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
Date: 2016-10-30 16:39:11.205
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\P EAuth.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
Date: 2016-10-30 16:38:47.742
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\audiodg.e xe because the set of per-page image hashes could not be found on the system.
Date: 2016-10-26 14:14:35.774
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\audiodg.e xe because the set of per-page image hashes could not be found on the system.
Date: 2016-10-26 13:47:35.019
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\audiodg.e xe because the set of per-page image hashes could not be found on the system.
Date: 2016-10-26 13:25:50.931
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\audiodg.e xe because the set of per-page image hashes could not be found on the system.
==================== Memory info ===========================
Processor: AMD Athlon™ 64 X2 Dual Core Processor 6000+
Percentage of memory in use: 45%
Total physical RAM: 4095.3 MB
Available physical RAM: 2213.28 MB
Total Virtual: 8188.78 MB
Available Virtual: 6141.7 MB
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment