Windows 10 Related Program Lags

[anonymoose14]

Recently just gaming and studying on my pc, suddenly I noticed a longer boot up time than normal when I opened it this morning, I thought it was normal. But, when I opened apps like Chrome, file explorer, settings, everything was either delaying, not responding, or showing errors. I can still game normally so it is not hardware problem. The problem is with the (I think) windows related stuff like properties of files not opening, task manager and cmd on admin showing "This operation returned because the timeout period expired", some apps showing "The remote procedure call failed", Chrome lagging when interacting with file explorer to upload files. I think it has to do with corrupted files but not sure.

Just a heads up that when I am having problem with my pc I try to troubleshoot it first with what I can search but I ran out of options that's why I am here. I tried sfc /scannow, DCIM and getting back to my restore point but it states that it was corrupted. I do a fresh restore point everytime I update windows.

I hope anyone can help with my problem! Thanks!

Tried using Tweaking but it only opens and runs on safe mode. It doesn't seem to fix the problem. I can't even attach a file here since it is interacting with file explorer. It shows the error "This operation returned because the timeout period expired" for the tweaking repair tool just like it does on admin cmd.

[Boggin]

Which antivirus program are you using ?

Can you open a Command Prompt (Admin) and enter these cmds and let me know if they resolve.

If you can't open a cmd prompt then go Start - type powershell, right click on Windows Powershell and select Run as administrator.

dism /online /cleanup-image /startcomponentcleanup

dism /online /cleanup-image /restorehealth

sfc /scannow

shutdown /r /t 00

It could be because of an infection, so if those cmds allow you to open a program, boot into Safe Mode with Networking and run a scan with the ESET Free Online Scanner.

https://www.eset.com/uk/home/online-scanner/

Let me know if it finds anything and reboot again after coming out of Safe Mode to see if your boot up time and performance improve.

If things don't improve then run a scan with AdwCleaner. - https://www.malwarebytes.com/adwcleaner/

[anonymoose14]

Thanks for the reply! I'm using only windows defender.

As stated windows apps trying to be opened as admin doesn't work due to the error timeout period expired. I did try the commands at safe mode but getting stuck at restorehealth due to error 0x800f081f, but I did try to fix it but met a dead end when fix should not be done on safe mode. Done the eset and malwarebyte, both detected errors on files and registry, fixed it, run it again, states that pc is clean, but the problem still persists.

[Boggin]

So were you able to run a Command Prompt (Admin) in Safe Mode ?

Can you create Win 10 install media (DVD or USB) after reading the instructions at https://www.microsoft.com/en-gb/software-download/windows10

If you can do that, boot up with it and navigate to the Install screen and click on Repair your computer.

Navigate to the Recovery Environment and select Command Prompt and enter -

bcdedit |find "osdevice"

For clarity that is a Pipe symbol before find and is the uppercase of \

Using your partition letter instead of the X I have exampled, enter -

sfc /scannow /offbootwindir=X:\ /offwindir=X:\Windows

Note the space before each /

Enter exit to close the cmd window, remove the install media and reboot to see if that has resolved.

[anonymoose14]

Good day! Just done the install media and boot with the usb.

I entered the bcdedit and it did nothing, is it normal?

Entered the "sfc /scannow /offbootwindir=c:\ /offwindir=c:\Windows" or any partition letter and it just showed details of the sfc and its attachments like /scannow /verifyonly /scanfile, etc. It also showed what the attachments does like scans integrity of all protected system files... So just the details. Is it normal?

I still proceeded and reboot, but still the same so i think it didnt work.

[Boggin]

It should have returned with -

Microsoft Windows [Version 10.0.18363.592]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcdedit |find "osdevice"
osdevice                partition=C:

C:\WINDOWS\system32>

Did you enter the cmd correctly ?

[anonymoose14]

oh that definitely is different.

but in cmd under the startup repair the left side is like X:\Sources>, windows is installed at my local disk c:. don't know if that affects it.

[Boggin]

When you boot up with install media it doesn't always see the volume as in C:

Have you tried the bcdedit cmd again ?

[anonymoose14]

Done it again and nothing happened.

[Boggin]

I don't know why that is not returning with the partition letter - never came across that before and you normally only get those sfc details when you had made a typo in the cmd.

Can you show me pics with the sfc cmd using D: and E:

[anonymoose14]

Is this what you mean?

[Boggin]

I think you are going to have to perform a Reset where you can retain your personal stuff but will need to reinstall all of your programs, so if you have any paid for programs then ensure you have their product keys.

An icon is put onto the desktop after that operation which lists all of the programs it has removed.

Your system seems to be all to hell, possibly because of the infections, but when you boot up with install media you aren't booting into Windows but into Memory.

[anonymoose14]

  Seems like it is beyond help. But anyways, thank you very much for your help and time mr/maam Boggin, really appreciate it. Ill just try and look for someone to check it personally as a last resort. Cheers!

[Boggin]

I was thinking you had already done this but you haven't.

An alternative you can try is a repair install which doesn't affect personal stuff or installed programs.

If you can, open Windows/File Explorer - This PC - insert the install USB and double click on its drive.

This will open to its files where you then double click on setup.exe Application

As the infections seem to have damaged files, then this should put them right - hopefully.