Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

FRST Logs


  • Please log in to reply

#46
Rodger899

Rodger899

    Member

  • Topic Starter
  • Member
  • PipPip
  • 45 posts

Here is the additions

Attached Files


  • 0

Advertisements


#47
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,912 posts
  • MVP

I think we got it.  The last SRU error was at 6:43 and we have an unrelated newer error at 7:23 which is usually associated with a reboot so no new SRU error.

 

It is complaining about a bad driver.  Search for

device manager

hit Enter

Click on View, Show Hidden Devices

Then look down the list of devices for one marked with a yellow or red flag.  If you find it, right click on it and select Properties then Details.

Change the value in Property from Device Description

to Hardware IDs

Select the first value and right click and Copy then cancel.

Move to a reply and Ctrl +v and the copied value will appear.

 

If there is more than one flagged device then repeat for each.

 

While in Device Manager, open Network Adapters and look for any that mention Bluetooth.  If you see one then go in to its details and copy its Hardware ID.  Also look under Driver and give me the date and version.

 

Let's run dxdiag:

In the Search box type:  dxdiag 
 
wait for it to find it.  Right click on dxdiag.exe and Run As Admin.
Yes
Once it finishes (green line in bottom left goes away)
 
Save All Information.  Point it at your desktop and it should save it as dxdiag.txt.
 
Exit
 
Attach dxdiag.txt to a Reply.

 

 

There is an LSA error:

 


Error: (09/25/2021 09:35:39 AM) (Source: Microsoft-Windows-Directory-Services-SAM) (EventID: 16953) (User: NT AUTHORITY)
Description: The password notification DLL C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (<drive>:\<path>\<filename>.<ext>) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files.  Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft..../?LinkId=245898.

 

 

As you no longer have TrueKey installed (this is a password manager that you get sometimes foisted on you.  First x passwords it saves are free then you have to pay for more. ) it is just a remnant from a poorly written uninstaller.  We can remove the entry with a fixlist.  

 

 

Attached File  fixlist.txt   354bytes   1 downloads

 

This will need to reboot but should be very quick otherwise.

 

Rescan with FRST and attach the logs.

 

 


  • 0






Similar Topics

10 user(s) are reading this topic

0 members, 10 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP