Error 0x80070002 ... verifying known folder

[soho1]

Hi, I have had this Gateway DX4831-01e for a couple weeks now and see warning messages in the event log like this:




Error 0x80070002 occurred while verifying known folder {fdd39ad0-238f-46af-adb4-6c85480369c7} with path 'C:\Windows\system32\config\systemprofile\Documents'.

• The messages occur often.
• They occur even for files that I have never visited, although the Index Manger or some other system component may be looking at.
• They messages occur back when the system was setup at the OEM prior to shipment and availabilty for sale at the retail store.

Gateway support seems to be of no use. I can only reach a typical first tier technician who laughably wanted to blame viruses. They do not seem to comprehend that the errors started in the OEM install, prior to shipping the PC for sale. (See the attached log)

At the Gateway support site, I self-downloaded all of the currently available hardware drivers and made sure that the system was updated.

All Windows updates have been applied.

I have attached a copy of the events to this post.

So, what is Windows Home Premium 64-bit really complaining about and how do I fix this?

 

[pebbly]

Hi soho1 have a read of this You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services it also gives you the oppertunity to download Microsoft fixit centre

 

[soho1]

Trying that out. I will report back with results.

 

[soho1]

Still getting those errors since the FixIt (non-agressive):

Error 0x80070002 occurred while verifying known folder {b4bfcc3a-db2c-424c-b029-7fe99a87c641} with path 'C:\Windows\system32\config\systemprofile\Desktop'.
Error 0x80070002 occurred while verifying known folder {fdd39ad0-238f-46af-adb4-6c85480369c7} with path 'C:\Windows\system32\config\systemprofile\Documents'.
Error 0x80070002 occurred while verifying known folder {625b53c3-ab48-4ec1-ba1f-a1ef4146fc19} with path 'C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu'.


Going to try the non-recommended agressive mode now:

 

[pebbly]

Still getting those errors since the FixIt (non-agressive):

Error 0x80070002 occurred while verifying known folder {b4bfcc3a-db2c-424c-b029-7fe99a87c641} with path 'C:\Windows\system32\config\systemprofile\Desktop'.
Error 0x80070002 occurred while verifying known folder {fdd39ad0-238f-46af-adb4-6c85480369c7} with path 'C:\Windows\system32\config\systemprofile\Documents'.
Error 0x80070002 occurred while verifying known folder {625b53c3-ab48-4ec1-ba1f-a1ef4146fc19} with path 'C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu'.


Going to try the non-recommended agressive mode now:

good luck wth that soho1 , hope it works out for you

 

[soho1]

No good. Even after agressive mode, I am still getting these errors.

 

[jonnyhotchkiss]

Old post, but issue is still prevalent, and not marked as solved...

If this works, credit is due to myurkus and DOrzx

(quicktip: computer management > local users > users > YOU > properties > Profile 'home folder' local path = c:\users\you

Assume religious position > pray

 

[jonnyhotchkiss]

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

UPDATE: for me, adding the profile home path as recommended did not stop folder verification issues re desktop @

C:\Windows\system32\config\systemprofile\Desktop.

Manually attempting resolution.

the culprit

Notice the absence of a parent.

Glanced at other GUIDs, noticed recent's parent ({3EB685DB-65F9-4CF6-A03A-E3EF65729F3D}, a candidate for our orphaned Desktop)

A quick peek at Nirsoft's SpecialFoldersView shows a few familiar faces, everything looks hunky dory.

In comparison, here's my pictures

notice no parent, and also the parsing name...

My Music ::{59031a47-3f72-44a7-89c5-5595fe6b30ee}\{4BD8D571-6D19-48D3-BE97-422220080E43}
My Pictures ::{59031a47-3f72-44a7-89c5-5595fe6b30ee}\{33E28130-4E1E-4676-835A-98395C3BC3BB}
My Videos ::{59031a47-3f72-44a7-89c5-5595fe6b30ee}\{18989B1D-99B5-455B-841C-AB7C74E4DDFC}
Documents ::{59031a47-3f72-44a7-89c5-5595fe6b30ee}\{FDD39AD0-238F-46AF-ADB4-6C85480369C7}
*Downloads + Favorites break the mould (no parsing parent)

Proposal #1: Change (add) Desktop's parsingname to

::{59031a47-3f72-44a7-89c5-5595fe6b30ee}\{B4BFCC3A-DB2C-424C-B029-7FE99A87C641}

I really wish I knew when to expect the event, re debugging... opening explorer, visiting desktop et al does NOT generate folder verification error. PID? SearchIndexer?! Now that's interesting...

 

[jonnyhotchkiss]

OK so I've got windows search set to manual. I stopped it. I was looking at other stuff MS gets wrong (parked CPUs, WLAN AUTOConfig "warning" re a service successfully stopping, event 37 The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 20 seconds since the last report....) and then and then out of nowhere the event occurred.

Sadly, this suggests the nice clean cause/fix of setting the user's home profile path is debunked, as it were.

One really interesting thing I've only just noticed for the first time today looking at all this is that it SEEMS that, to get the CAUSE, ie a Process ID, you have to add the Process ID column. That info does not seem to appear elsewhere in event summary.

UPDATE - also under "friendly", ie

Execution

[ ProcessID] 6236
[ ThreadID] 7880

So I could just stop windows search, ie disable the service...

keen to learn what others are experiencing, ie which paths/GUIDs, if only in 64-bit windows... if service packed...

 

[jonnyhotchkiss]

OK, so I've booted up my other "clean build". The goal: to reduce event errors and warnings to an "acceptable" threshold*.

First thing is to see what paths I've previously created in attempted to resolve this.

I've added the date accessed column, which suggests none are needed, but let's not go breaking bad yet.

Windows Search is started (manual), Service Pack 1 is installed (the only known significant difference between this build "crash", and it's sister-with-the-bad-known-folders, "crash 2")

 

[jonnyhotchkiss]

apologies to all internet users googling this, trying to find solutions, only to discover the litter I've left everywhere.

If it's any consolation, I think it's caused by a suspect user profile path. Adding the "Process ID" column gives a quick glimpse of which process invoked the error-event, ie Windows Search (compare with the PID in Task Manager).

The root cause appears to be this, the NT Authority User Profile

I don't feel like messing with this right now though, so for the time being, created dummy folders, disabling windows search, or just ignoring the errors all sound like good ideas