Cleaning Memory Before Starting Repairs FAILS

[radar]

While running Tweaking repairs in SAFE MODE, I get this message, below.  How do I fix whatever is causing this repair to fail a few times before completing? 

thanks, radar

────────────────────────────────────────────────────────────────────────────────
────────────────────────────────────────────────────────────────────────────────

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
────────────────────────────────────────────────────────────────────────────────
Memory Total: 63.15 GB
Memory Used: 2.85 GB(4.5145%)
Memory Avail.: 60.30 GB
────────────────────────────────────────────────────────────────────────────────

Starting Repairs...
   Started at (7/4/2026 1:55:18 PM)


The current repair has failed to start for over 30 sec.
Trying Again....


The current repair has failed to start for over 30 sec.
Trying Again....


The current repair has failed to start for over 30 sec.
Trying Again....

   Done, but failed, at (7/4/2026 1:57:18 PM)
   Total Repair Time: 00:02:01

The current repair has failed to start 4 times.
Something is keeping the repair from running.

Try running the repairs in Windows Safe Mode. (This will keep 3rd party programs from getting in the way of the repairs)
If the repairs still fail then please post in the Tweaking.com forums for support.

[garioch7]

@radar,

This Forum seems pretty dead to me.  I would not expect any replies from the new owners of Tweaking.com.

If your computer is Windows 11, or a Windows 10 with all of the updates, it appears that the "REPAIR" program is not being maintained.

If that is so, it is dangerous to run it on those two versions of Windows.  Every monthly Windows Update changes Windows, and a repair program that is not being constantly updated is bound to fail at some point in time.

I would recommend ceasing to use the product.  I had a licensed version that I ceased using years ago when Shane CROFT, the developer, left the company, to start his own company.

I hope I am surprised, and you get a reply from the new owners.  I visit here daily, and have never seen anyone reply to users.  As you can see, the Forum is pretty locked down, except for spam, which is cleaned about monthly.

Have a great day.

Regards,
Phil

[jason.reid]

Hi radar,

Sorry for the slow response here.

That message means the repair process couldn't launch its child process - it's almost always something holding a lock rather than a fault in the repair itself. A few things to check:

• Run from an account with full admin rights ? right-click the shortcut, Run as administrator, even in Safe Mode.
• Safe Mode with Networking vs. plain Safe Mode ? try plain Safe Mode if you haven't; some services still load in the Networking variant.
• Security software ? if you have an AV or EDR agent with a boot-time driver, it can still be active in Safe Mode and block the repair launcher. Temporarily disabling it is the usual fix.
• Run the repairs one at a time rather than as a full set. That will tell us which specific repair is failing to start, which narrows this down a lot.

If you can post which Windows build you're on (winver) and the result of running a single repair on its own, I'll take it from there.