Click here for important information about

How to fix a failure to launch ?

November 29, 2020 at 01:51:21
Specs: x32 Win10 v2004, 4Gb
In x32Win10Prov20H2, sometimes programs that are set to launch with windows, don't; nor can they be launched till after a reboot. What to tweak to remedy this ?


See More: How to fix a failure to launch ?

November 29, 2020 at 08:27:54
These are long shot possible solutions...; no harm to tyr them?

Run ccleaner (free version) and let it clear out assorted junk, cookies, history files.

When you install it use the manual/custom option - NOT the default, proffered option. Watch for and uncheck all pre-checked boxes - other than the one for ccleaner itself. That way you avoid unwanted additions, system changes etc..

With all power removed completely, remove RAM modules and clean their edge contacts. Use a soft pencil style eraser, and then wipe the edges with a soft lintless cloth (or soft facial tissue); use nothing abrasive to clean or wipe...

Replace one module (if more than one present; insert it firmly. Then remove it, wipe edge connector; reinsert again firmly. again remove it; wipe edge connector again and then reinsert module firmly and leave there.

Power up and see if situation improves/resolves...

Repeat RAM cleaning process with a second module (if exists) and use that in place of the first - which logically you remove first... (again with "all" power removed). Do the insert/remove routine as above and test system with that module in place alone.

If all still OK - or not - again with all power removed, reinsert the other module (if there is one).

Power up and see what the situation is then?

Why insert, remove, reinsert RAM module? To clean the internal contacts on the RAM sockets on the motherboard - at least as best as can be done...

What you're describing in some respects can often be due to RAM not being fully seated in its sockets; or oxidised contacts - hence the cleaning routine as above. Even failing RAM... The latter is why you try each module/stick in turn - to isolate a possibly failing module/stick - if exists.

A failing psu ican also produce the situation you describe, although that's more likely to show up at bootn up... Smoothing capacitors in the psu can start to leak, and a power recycle allows them to seal due to the first boot and then apparently work OK on the second at the time. After cool down/power off period the leak csn/usually will reoccur...

But try the ccleaner routine and RAM cleaning and see if they help?

Possible the shortcut you have is equally duff; so maybe delete it. Then fully power cycle (power down, power back up and recreate it)?

Reply ↓  Report •

December 1, 2020 at 02:15:27
I was looking for a remedy specific to the phenomenon rather than a general maintenance suggestion. The shortcuts ARE functional - except SOMETIMES.


Reply ↓  Report •
Related Solutions

Ask Question