Windows 10 Just A Moment Please

[cburns530]

Well it all started Friday night when I started to notice my internet connection was a little sluggish on my laptop while doing some gaming while it worked fine on everything else. Not thinking anything of it I just kept playing and figured it would work itself out. Well anyways earlier today I was playing games again and I realized wow my connection is doing really bad. So I decided I would clean my computer with Ccleaner and Glary and then restart and hope to see if it might improve any. Well it went from bad to horrible. As I rebooted it up I noticed windows was acting different and then I got the "Windows failed to load properly and all of that fun stuff where your able to factory reset, Windows automatic repair etc. Figuring my laptop was slightly overdue for being reset, I factory reseted and due to previous experience I knew it wouldn't take very long after the initial wipe. I factory restored my pc, booted windows 10 and chose location, WiFi and then my laptop got stuck on Just A Moment... it has been that way for about 3 hours until I decided it may have gotten bugged so I just redid the process except I went out of the Just a Moment... and put my laptop into safe mode. And the problem is still occurring once again. I have a older laptop, Toshiba Satellite i3 2260 or something similar, 8gb ram, previously upgraded from Windows 7 in about June. Thank you for any solutions you have

 

[Lutfij]

Initial concerns are,

I factory restored my pc...and put my laptop into safe mode.

are we dealing with a PC or a laptop? To find the root cause of your issue we'd need to know the model number for your laptop. It could be easier on you if you followed through the drop down menu selection, here, to locate your laptop + find compatible drivers and/or BIOS updates.

I'd also ask you to make sure your installer for Windows 10 hasn't been corrupted by creating a bootable USB installer and following this guide to perform a clean installation of Windows 10 outside the upgrade path.

If what you're saying is true then it seems that your system was most likely undergoing a Windows update for which the best course of action would've been a system restore prior to the point the issue cropped up.