Member Avatar for acuariano

this morning everything was ok
i downloade the latest update for diskeeper and when trying to install i got the error message: I HAVE WINXP/SP2
"ERROR 1402 could not open key. unknown drfg....CLSid
then i try to open the program from desktop and
this is the error message when i try to open/initializa diskeeper 9
MMC can not open the file C:\Programfiles\ExecutiveSoftware\Diskeeper\Diskee per.msc.
this may be because the file does not exist,is not an MMc console,or was created by a later version of MMC.this may also be because you do not have sufficient access rights to the file

any help please would be appreciated
thanks

  • 2 Contributors
  • 2 Replies
  • 285 Views
  • 22 Hours Discussion Span
  • Latest Post Latest Post by acuariano

Dani AI

Generated

As correctly suggested, this kind of installer/MMC failure on older Windows systems most often comes from incorrect registry ACLs — the installer can’t open a protected key and the MMC snap‑in won’t load. Two practical, safe approaches are: (A) fix the specific registry key ownership/permissions that the installer reports, or (B) reset the registry ACLs back to admin/system ownership and retry. Both require an administrator account and a registry backup. (support.gfi.com)

Before any change: create a System Restore point and export the registry (Regedit → File → Export). Then log on as a local Administrator and, if the installer shows a GUID, use Regedit’s Find to locate that GUID under the Registry hives. Right‑click the parent key → Permissions → Add “Administrators” and “SYSTEM” → give Full Control. In Advanced → Owner, set the owner to Administrators and enable “Replace owner on subcontainers and objects” and “Replace all child object permissions…”. After applying, retry the install. ()

If many keys are affected, the Microsoft SubInACL approach automates resetting ACLs. Save the following as a .cmd in the Resource Kit Tools folder and run it from an elevated command prompt (it can take several minutes):

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f /grant=system=f

Obtain SubInACL from a trustworthy source, back up first, and reboot when done. (learn.microsoft.com)

If manual fixes or an ACL reset aren’t possible, use an installer obtained directly from the vendor (they sometimes repackage installers to avoid broken ACLs) or contact support. These steps are standard, low‑risk ways to restore installer and MMC behavior without reinstalling Windows.

Recommended Answers

All 2 Replies

Member Avatar for JoetjeF

Have you downloaded the latest version of Diskeeper? Version fixes this problem. It's a registry permission problem.

Member Avatar for acuariano

yes,support e-mail me a new full version...evrything is ok now...thanks

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.