Share via


Windows Event ID 10005 Error

Question

Monday, February 13, 2017 6:50 PM

I have been getting event id 10005. I have been looking everywhere for a fix, but nobody seems to have a fix that works for me.

Event Details: pastebin.com/3Bn7R3Un
(Screenshot of above link)

fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=18736f25-3df9-4430-9a8f-8c5f4e189f2e

Anyone know a fix? I can provide any additional information as needed. Thanks.

All replies (8)

Tuesday, February 14, 2017 8:21 AM ✅Answered | 2 votes

Hi, 

This issue could be caused that that the registry key for system profile HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18 was missing or corrupted.

To workaround this problem, merged the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18  from the working machine. 

To change the registry keys, please backup it first. 322756  How to back up and restore the registry in Windows

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Tuesday, February 14, 2017 8:39 AM

Install all updates, run sfc /scannow, change profile and see.


Tuesday, February 14, 2017 5:52 PM

Would a VM of windows 10 generate a working key to work with?


Wednesday, February 15, 2017 5:30 AM

Hi, 

Yes, it could be OK. Please make sure you get the key from the same edition of Windows 10. 

Also, we can directly find the key in the reference System and then, right click the Export the Key, then Import to your own PC. 

Hope it can be helpful on your issue. 

If this issue still persists, we may need to use Process monitor to capture the system events during you are search something on this PC, then, let's see which files or keys block wsearch.exe. 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Wednesday, February 15, 2017 3:41 PM

Alright, I will create a VM of my current windows 10 version, and retrieve that key.

I'll reply back once I have results


Wednesday, February 15, 2017 5:28 PM

Alright. I have merged the new/fresh key I obtained from the VM with my old one.

So now I just wait and see if the error persists?


Thursday, February 16, 2017 1:50 AM

I did run a scan and it actually did find some corrupt files and fixed them successfully, though I don't think it solved my issue. Still, Thanks


Friday, February 17, 2017 1:29 AM

Whatever, I will consider this fixed until I see it get logged again, thanks everyone who replied.