Suddenly Very Slow Boot Up - Windows 10 Running Ff

"Not recognized"

 

This is not good.
Let's try running Command Prompt.
Go to C:\Windows\System32\ and you'll find cmd.
Right-click > Send to > Desktop (create shortcut)

 

Update: I finally got sfc /r to run but, after an hour, it was hung at 11%. Do I need a new drive?

I'm done for today and will resume tomorrow. Such things take an inordinate amount of energy, mental and physical, out of this badly bent old fossil.

 

Have you unplugged the machine and re-seated the RAM and any expansion cards?

 

No, I'm paralyzed.

 

Did not know that. Is there anyone who can? RAM modules working their way loose can cause wonky things.

 

This is exactly how I used to go to an elevated command prompt before I pinned it to the task bar. Once you get the elevated prompt open, you should hopefully be able to get some insight into the cause of your issue.

I understand you may have slight difficulty navigating some of the unfamiliar areas and apps on your system, but there are a few tools on a Windows OS designed to help analyze system performance, specifically. The Performance Monitor (perfmon.exe ) and Resource Monitor (resmon.exe) could prove to be a great help should your issue persist after running some of the previously suggested command line utilities. Hell... even Task Manager may at least give you an idea of what programs, processes, or services might be causing a bog-down of the system.

I'm crossing my fingers that just typing some of those commands in an elevated prompt will work for you. If not, I'm sure the community here can help walk you through the next best steps... and I think we helpers now understand we need to be more specific, thorough, and clarify a bit better. Screenshots, batch scripts... whatever it takes. We gotcha! I know its frustrating... but hey, you're learning some tech stuff as you go along, right?

 

Can one of you high-ranked, long-time MajorGeek members let me (and poor ol' DON GAYNOR) know whether or not this would make any difference at all considering his current situation?

Would it do any good for him to boot from a rescue disk to run these commands? I thought about suggesting booting up in safe mode and actually, depending on the cause for all this misbehavior, that may be worth a try as well... what do you guys think? General consensus? A few things seem to point towards onedrive as the culprit... booting into safe mode would exclude that program and any related services from loading... correct?

If any of you veterans think maybe the rescue disk might be a good way to go, DON would probably be very grateful for some visual guidance/direction ... which I guess is an arrogant, pompous way of saying 'screenshots would be cool...' Sorry... I like exercising my vocab to the point of being a bit Asperger.

 

Trex,

I've tweaked everything and gotten my system "livable", not perfect. I simply don't shut it down which saves me the long 9+ minute start up each day. It's not a solution but I am living with it.

Thanks to all who jumped in anyway. You folks are tops!

 

S-O-L-V-E-D-!

After applying all of your great tips and suggestions, my new cold boot time is currently 90 seconds. I am satisfied with that. You wonderful folks are awesome!

Thank sincerely.

Don

 

I *think* was the free version of WiseCare365.