Friday, December 13, 2013

Error 0x80070002 occurred while verifying known folder


Server is getting a general Warning message speradically a lot. Its a Warning so not a big deal but it does raise concern.
Here is the error:

- System
  - Provider
   [ Name]  Microsoft-Windows-KnownFolders
   [ Guid]  {8939299F-2315-4C5C-9B91-ABB86AA0627D}
   EventID 1002
   Version 0
   Level 3
   Task 0
   Opcode 0
   Keywords 0x8000000000000000
  - TimeCreated
   [ SystemTime]  2013-12-13T05:30:22.504632600Z
   EventRecordID 6590
  - Execution
   [ ProcessID]  10080
   [ ThreadID]  5392
   Channel Microsoft-Windows-Known Folders API Service
   Computer **********************
  - Security
   [ UserID]  S-1-5-18
- EventData
  hrError 0x80070003
  FolderId {B97D20BB-F46A-4C97-BA10-5E3608430854}
  Path C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup 

So yeah a lot of these are happening with various folders.


I was doing some reading and found out that this specific error had to do with some folders missing in a default profile area. One of the readings fixes was, make the missing folders. What a great idea.

There are several easy ways to make the folders:

Use can use the MD, make directory option.

MD "C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs"

Windows Explorer
Just go to the folder area and make the missing folder. Make sure you make the full path if more than one folder is missing.

Copy the Default profile on the system.
Every system has a profile that it uses as a template for making a new user profile. So I copied it and pasted it in the missing directory. Note: I did not verify that ALL the missing folders where there. I figured since its a warning, I will wait out the log file and see any othere missing folders show up.

Update: welp that didn't work.. Still getting Error

0x80070002 occurred while verifying known folder {b4bfcc3a-db2c-424c-b029-7fe99a87c641} with path 'C:\Windows\system32\config\systemprofile\Desktop'.

and it does exist.

So i did some more digging and ran across this post,,  about how there are 2 system folders in windows 64 bit.. I totally forgot this. So I copied the folders to the SysWOW64. I am thinking this will fix the issue. We shall see.

1 comment:

  1. comment attempt #2!

    the culprit (I suspect) is windows search, and the NT authority

    possible fixes: disable windows search (assuming that is the process responsible for the event 1002- to check add the process ID column in eventvwr.msc- and you don't use it - EVERYTHING is an excellent replacement)

    alternatively try and fix the NT AUTHORITY bad path? sounds like trouble to me though!