Question Windows 10 64 bit Apps crash before opening

[BoomerD]

This started a couple of weeks ago. Try to open any game or app, even native Windows apps, the start screen for the app will appear on the screen then close itself. Nothing shows up in Task Manager.

Firefox and Chrome work fine, MS Edge crashes. I've run malwarebytes in safe mode...can't open it in normal mode, nothing found. Windows Defender finds nothing except something in an app called "burnaware_free" which, as far as I can tell, I don't even have in my system.

I "backed up" a couple of weeks to a previous restore point...every thing seemed to work. Yesterday, this crap started again.

I REALLY don't want to have to reinstall windows if I can avoid it.

 

[Zoozuu]

you probably can't avoid reinstalling windows if you're getting app crashes. unless of course it's hardware that is causing the crashing. have you checked the error report section of the control panel to check out the errors that happened?

if you have a second harddrive I would install windows on that and see if a reinstall even would fix it. if you get the same errors from the second drive then i would say its hardware. if it works normally then it's your OS.

 

[BoomerD]

you probably can't avoid reinstalling windows if you're getting app crashes. unless of course it's hardware that is causing the crashing. have you checked the error report section of the control panel to check out the errors that happened?

if you have a second harddrive I would install windows on that and see if a reinstall even would fix it. if you get the same errors from the second drive then i would say its hardware. if it works normally then it's your OS.

I currently have 2 M.2 drives installed (1 is my OS drive, the other is a DATA drive) , a 240gb SSD (original OS drive when this started, just used ), and a 2tb HDD. I used the WD version of Acronis to clone the SSD to the M.2, so if there is a problem in one, it's now in both.

 

[VirtualLarry]

I used the WD version of Acronis to clone the SSD to the M.2, so if there is a problem in one, it's now in both.

You didn't leave both drives physically in the system after the clone, did you?

 

[BoomerD]

You didn't leave both drives physically in the system after the clone, did you?

ahem...yes.

 

[VirtualLarry]

ahem...yes.

At least back in the Win2000 days, that would horribly hose the system.

 

[BoomerD]

At least back in the Win2000 days, that would horribly hose the system.

Only it started this crap BEFORE I put the new NVME drive in the system and cloned it.