Jump to content

Ok to Delete? Why save registry? How to use saved Registry?

djkaraok

By djkaraok
in Software

 Share

Recommended Posts

djkaraok

djkaraok

Posted
Posted (edited)

Ok to delete?

Missing Shared DLL    C:\Windows\system32\MSCOMCT2.OCX    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls
Missing Shared DLL    C:\Windows\system32\MSCOMCTL.OCX    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls
Missing Shared DLL    C:\WINDOWS\System32\COMDLG32.OCX    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls
Unused File Extension    .psb - PhotoshopElements.PSBFile    HKCR\.psb
Unused File Extension    .pp3    HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pp3
Unused File Extension    .xmp    HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.xmp
ActiveX/COM Issue    PhotoshopElements.Application.11.1 - {6DECC242-87EF-11cf-86B4-444553540000}    HKCR\PhotoshopElements.Application.11.1
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{1EFB6596-857C-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{20DD1B9E-87C4-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{232E456A-87C3-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{2C247F23-8591-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{35053A22-8589-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Comdlg32.ocx    HKCR\CLSID\{3C4F3BE3-47EB-101B-A3C9-08002B2F49FB}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Comdlg32.ocx    HKCR\CLSID\{3C4F3BE5-47EB-101B-A3C9-08002B2F49FB}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Comdlg32.ocx    HKCR\CLSID\{3C4F3BE7-47EB-101B-A3C9-08002B2F49FB}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6352-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6353-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6354-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6355-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6356-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6357-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{586A6359-87C8-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{603C7E80-87C2-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{66833FE6-8583-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Comdlg32.ocx    HKCR\CLSID\{7629CFA2-3FE5-101B-A3C9-08002B2F49FB}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Comdlg32.ocx    HKCR\CLSID\{7629CFA4-3FE5-101B-A3C9-08002B2F49FB}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{8E3867A3-8586-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{B09DE715-87C1-11D1-8BE3-0000F8754DA1}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{BDD1F04B-858B-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE32-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE33-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE34-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE35-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE36-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE37-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE38-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE39-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE3A-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE3B-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE3C-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE3D-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE3E-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE3F-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE40-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE41-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\Mscomctl.ocx    HKCR\CLSID\{C27CCE42-8596-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{C74190B6-8589-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{DD9DA666-8594-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\mscomctl.ocx    HKCR\CLSID\{F08DF954-8592-11D1-B16A-00C0F0283628}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWOW64\comdlg32.ocx    HKCR\CLSID\{F9043C85-F6F2-101A-A3C9-08002B2F49FB}
ActiveX/COM Issue    InProcServer32\C:\Windows\SysWow64\MSCOMCT2.OCX    HKCR\CLSID\{FE38753A-44A3-11D1-B5B7-0000C09000C4}
Missing MUI Reference    C:\Users\djkaraok\AppData\Local\Mozilla\Firefox\Mozilla Firefox\updates\0\updater.exe    HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache

When ask if I want to save registry I understand it is to be a backup in case I delete something that will crash my system but how would I use it if my registry is damaged how do I get to the backup file?

 

Thanks

Edited by Nergal
added code tags
Link to comment
Share on other sites
  • Moderators
mta

mta

Posted
  • Moderators
Posted

"OK to delete?"

Well, really, that's up to you to decide.

All I can say, as stated before on this forum, CC is one of the more 'gentle' cleaners, and personally I have not had an issue with it cleaning my PC or the registry.

But - there is a danger, albeit small, that things can go pear shaped (hmmm, I just got the reason for the Piriform logo maybe) and that is why there is the Do you want to backup changes to the registry? option.

 

It creates a .REG file of what it is about to change so if it goes belly-up, you have a backup.

Since it is a .REG file, double clicking it will reload those registry entries.

Backup now & backup often.
It's your digital life - protect it with a backup.
Three things are certain; Birth, Death and loss of data. You control the last.

Link to comment
Share on other sites
  • Moderators
Nergal

Nergal

Posted
  • Moderators
Posted

the best advice for your situation can be found below this sentence in my signature.

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites
  • Moderators
Andavari

Andavari

Posted
  • Moderators
Posted (edited)

Most likely some program you've uninstalled at some point also took those System32 files out with the uninstall - unproperly of course because it didn't bother to unregister them. And many uninstalls will offer to remove them, completely in error though.

 

From experience those files should not be removed because it will eventually cause a problem with a software complaining about those missing files since there's still is a plethora of software that require them function.

 

Luckily if the registry references are removed the files can later be re-installed back into System32, and re-registered into the system using Windows built-in tool Regsvr32 via Start->Run:

regsvr32 "C:\WINDOWS\System32\COMDLG32.OCX"

regsvr32 "C:\Windows\system32\MSCOMCT2.OCX"

regsvr32 "C:\Windows\system32\MSCOMCTL.OCX"

 

Edit:

I see from the posted info there's also references to them in "C:\Windows\SysWOW64". Personally I wouldn't remove those references, bound to cause you issues!!!!! And I would hunt down a way to physically restoring those files onto the hard disk into the proper areas if they really don't exist in those paths you posted - either from System File Checker ("SFC"), or elsewhere.

Edited by Andavari
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept