SHGetPropertyStoreForWindows not found report

[Bob2c]

I have started getting the following report when I start my windows Vista Premium..SHGetPropertyStoreForWindows not found report..and ||Cannot make any sesnse of it. I am currently having some trouble with a gaming site but cannot attribute this message to it. Can you help?

 

[Bob2c]

Shell32.dll. is where this file should have been found. I have recovery disks but not sure how to repair the file if possible so help please.

 

[strongm]

Run command prompt as administrator and try

sfc /scannow

 

[Bob2c]

Still getting the message, have found the file and Norton File Insight gives it the thumbs up. Do you know what the GetPropertyStoreForWindows is for? I was going to try and replace the shell32.dll file to see if that cured it but my vista backup disks need a password and I can't remember it! Vista Premium is the operating system.

 

[strongm]

Yes, but knowing won't really help you: it retrieves an object that represents a specific window's collection of properties, which allows those properties to be queried or set

 

[Bob2c]

Here are the fault entries from my scannow results, very mysterious

015-11-21 13:38:16, Info CSI 000001b8 [SR] Beginning Verify and Repair transaction
2015-11-21 13:38:46, Info CSI 000001ba [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-11-21 13:38:53, Info CSI 000001bc [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-11-21 13:38:53, Info CSI 000001bd [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"

2015-11-21 13:39:20, Info CSI 000001bf [SR] Verify complete
2015-11-21 13:39:25, Info CSI 000001c0 [SR] Verifying 100 (0x00000064) components

2015-11-21 13:43:44, Info CSI 000001e1 [SR] Beginning Verify and Repair transaction
2015-11-21 13:44:00, Info CSI 000001e2 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store

2015-11-21 13:44:00, Info CSI 000001e3 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store

2015-11-21 13:44:06, Info CSI 000001e5 [SR] Verify complete
2015-11-21 13:44:13, Info CSI 000001e6 [SR] Verifying 100 (0x00000064) components

2015-11-21 13:47:46, Info CSI 00000218 [SR] Beginning Verify and Repair transaction
2015-11-21 13:47:46, Info CSI 0000021a [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-11-21 13:47:46, Info CSI 0000021b [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store

2015-11-21 13:47:46, Info CSI 0000021c [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store

2015-11-21 13:47:47, Info CSI 0000021e [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-11-21 13:47:47, Info CSI 0000021f [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"

2015-11-21 13:47:47, Info CSI 00000221 [SR] Repair complete
2015-11-21 13:47:47, Info CSI 00000222 [SR] Committing transaction
2015-11-21 13:47:49, Info CSI 00000226 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

 

[strongm]

Are you actually using the sidebar and gadgets? If so, see this advisory:

https://technet.microsoft.com/library/security/2719662

and this fixit (which disables the sidebar):

https://support.microsoft.com/en-us/kb/2719662

at which point you can safely ignore the sidebar errors in the SFC log file (and eliminate the sidebar as the source of the SHGetPropertyStoreForWindows messages)

 

[Bob2c]

I never use it. Brought it up in error once along time ago.

 

[strongm]

Fine, feel free to apply the fixit to disable it then

 

[Bob2c]

Done

 

[Bob2c]

Restart....No different, procedure entry point SHGetPropertyStoreForWindows not found. Host app not working reported also

 

[rclarke250]

This is from Microsoft forum.: this is 2 years old, so I don't think M$ did anything about it.

It appears the actual culprit is KB2685811, which is part of cumulative update KB2761494 that contains KB2685811
KB2685813
KB971286

Here is what sysnative.com Administrator niemiro has to say about this update:
"[T]his problem arises because these mof files [C:\Windows\system32\wbem\Wdf01000Uninstall.mof and Wdf01000.mof] have a duel "ownership" by ..._microsoft-windows-wdf-kernellibrary_... and ..._microsoft-windows-wdf-kernellibrary-mof_..., and the hashes for the same file by those two owners do not match. then gets all confused. There are a couple of ways this can go.

Firstly, either the hashes are meant to match, or they aren't. If they aren't, then we need to identify why is becoming confused, and what corruption is making it confused. Otherwise, we must make the hashes match. Now, just modifying the hashes to force a match is not a good idea, and will just break the chain further down (i.e. it is likely to push the problem off and onto Windows Update).

I now think, however, the problem is that in the latest cumulative update, the .mof files were updated. The hashes for ..._microsoft-windows-wdf-kernellibrary_... were updated, but the hashes for ..._microsoft-windows-wdf-kernellibrary-mof_... were not, by accident. would then try to match against two different versions of the files, which will never match. Therefore, the trick is to create a whole other version key in ..._microsoft-windows-wdf-kernellibrary-mof_... (several places in the registry), with the correct hashes, to fix what should have been there. will then be matching the correct hashes for the correct file, and all will be well."

I like to keep my Vista 32-bit system updated with the latest fixes, but after uninstalling cumulative update KB2761494, the previous problem I had with sfc /scannow is now gone.

It behooves Microsoft engineers to fix cumulative update KB2761494 to prevent this problem with other Vista systems. At the moment, I've hidden KB2761494 because windows update kept asking for me to install it again.

I don't like my Vista computer to be without updates, but I also want sfc /scannow to run error free.

The ball is in Microsoft's hands now. Hoping to see a repair soon.

 

[Bob2c]

Well I went to my local PC shop, and they quoted me some prices from £50 upwards to sort it out but it ment a wait of at least three days with the possibility of a further wait if it had to be sent away, with another charge for that. To cut a long story short, I bought a new one! Techie coward..LOL. But seriously, they took my hard drive out and connected it up to their machine and got access to the files etc and so it was still in reasonable shape. I will try and save the OS with the erecovery software and see if that repairs the system32.dll file after putting a copy of it all on my new computer. THANKS TO ALL for your help.

 

[Bob2c]

Trying to save it!.... the diagnostics has reported that the boot config data file is corrupt???

 

[Bob2c]

The dvd drive will start to install the XP disk but runs for about a minute and then stops. Meaning that it can see the disk and read from it. When I put the Acer recovery disks in, it does nothing and so cannot see them as far as I can make out so they must be faulty!