Recycle Bin Missing From Desktop, Can't Restore

Hi all,

My Recycle Bin missing from my desktop, and I can't restore it. I have tried all the fixes as listed on Microsoft's site at

http://support.microsoft.com/default.aspx?scid=kb;en-us;810869

I have also tried Kelly's Korner fix and Doug Knox's fix. I am stumped at this point. The option to add it under "customize desktop" is missing as well. All help is greatly appreciated.

Thanks, Tarheelfan001

 

First, copy the following script and paste it into a Notepad session and save it as RBkeyDelete.reg

Code:

REGEDIT4

[-HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}] 

Double click that saved file and OK its action when asked. That will clear the Recycle Bin Key entry in the Registry and all corruption will be gone.



Next, copy the following script and paste it into a Notepad session and save it as Recycle.reg

Code:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Desktop\NameSpace\{645FF040-5081-101B-9F08-00AA002F954E}] 
@= "Recycle Bin "

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}]
@= "Recycle Bin "
 "InfoTip "= "Contains deleted items you can permanently remove or restore. "

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\DefaultIcon]
@= "shell32.exe,31 "
 "Empty "= "shell32.exe,31 "
 "Full "= "shell32.exe,32 "

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\InProcServer32]
@= "shell32.exe "
 "ThreadingModel "= "Apartment "

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\ShellFolder] 
 "Attributes "=hex:40,01,00,20

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\shellex]

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\shellex\ContextMenuHandlers]

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\shellex\ContextMenuHandlers\{645FF040-5081-101B-9F08-00AA002F954E}] 
@=" "

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\shellex\PropertySheetHandlers\{645FF040-5081-101B-9F08-00AA002F954E}] 
@=" "

Double click that saved file and OK its action when asked.


Since the above was compiled under duress to answer a specific need and to replace a specific earlier file that was removed, I will offer an alternative to doing all that work yourself. I now offer a Regfile to download and run or run from the download site. Either way it will do all of the above and a little more to ensure that your Recycle Bin registry script is put in proper order in one easy execution.Get BinRepair.reg here.

 

EDIT:
[SIZE= "3"]If you are simply looking for a solution to the problem described in the thread topic, then you do not need to read this thread further.[/SIZE]

surferdude (who some may consider to be a knowledgeable geek) has edited his post #2 proposed solution above after research and testing was done.

The rest of the discussion in this thread pertains to

• a glitch in the Windows BBS forum software,
• and testing/pitfalls of registry cleaner utilities.

 

After some further testing on my "Test DummyXP" I find that the original Regfile posted will indeed cause multiple sub-keys to be created. That leaves the original sub-keys unchanged and adds sub-keys with the improper space in their string. That would mean any repair for those particular sub-keys would be ineffective. That certainly narrowed down the benefits that tarheelfan001 got from running the file. Considering that it worked for him, you can only wonder.

Then I took the opportunity of running RegSeeker and RegCleaner in their "Clean the Registry" and "Do Them All" modes. I dumped all inconsistencies that they found. Rechecking found that the flawed subkeys were still in there. So much for Registry cleaners.

Then I created a Regedit file to dump the entire CLSID\{645FF040-5081-101B-9F08-00AA002F954E} key. That removed all entries, good and bad. Then I ran the final version of the Rededit file posted earlier after it was created and amended with the help of noahdfear and mailman. That returned the key to the proper condition with no problems or duplicates.

I'll follow up by posting the cleanup Regedit file into the earlier post so the thread can be complete.

 

Thanks for your follow-up, surferdude.

Since I often use Macecraft's jv16 Power Tools 2007's Registry Cleaner utility and PeteC and charlesvar also have jv16PT (older versions?), I wonder how the jv16 PT's Registry Cleaner would perform in comparison to RegSeeker and RegCleaner.

jv16PT's Registry Cleaner has two modes: "Normal" and "Agressive "

I think jv16PT 2007's trial version is fully functional for 30 days. The Registry Cleaner utility appears to be newer than Macecraft's RegSupreme and RegSupreme Pro (according to the screen shots shown for RegSupreme and RegSupreme Pro). jv16PT's 2006 version's Registry Cleaner looked the same though back when I had it installed.

I don't have a test machine (yet) and I have Norton's Protected Recycle Bin so I am hesitant to try what you did with jv16PT.

If you'd like, I'll be happy to send you some cash via PayPal for your time to test jv16PT's Registry Cleaner after applying the originally posted REGEDIT4 merge.

 

mailman, I'll be happy to run those tests for no charge. I've downloaded them and will get to it this afternoon and report the results here.

 

OK mailman, I installed JV16 and RegSupremePro. They looked similar in many respects except that JV16 had several more features. The registry clean function appeared to be identical in all respects.

I ran RegSupremePro first. I chose the Agressive mode and when it completed gave me a health ration of 31%. I selected all it found and had it "Fix" them. Then I reran it, all settings the same, and it found nothing. It gave me a health rating of 100%.

I checked the Registry for the aforementioned sub-keys that had the spaces inserted in them. They were still there!

I restored the Registry from the backup that RegSupremePro made and ran the test with JV16 using the same settings. The results were the same and the inappropriate sub-keys were still there.

Evidently there is nothing untoward indicated by a space in a Registry key or sub-key that will be detected by a Registry Cleaner. I have now tested four of the leading ones with the same results.

ps. While doing this I noticed that the Registry Key named [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ had also been duplicated with one named [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\

I manually deleted it since. Anyone who used the original Regedit file that was posted here before the Administrator removed it will need to do that also.

 

surferdude,

Thank you!

I was hoping the jv16PT's Registry Cleaner would have done a perfect job. Wishful thinking, huh?

Looks like the only way to do a perfect job is to dig into learning how registries work and doing the job manually.


BTW, anyone reading this thread who is considering installing and running a registry cleaner application should read the discussion linked here before deciding whether to do so or not.