Nothing works on desktop after restarting

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 10 Home (OS Build 19041.329)
       #1

    Nothing works on desktop after restarting


    Hello, so this issues started a couple days back out of nowhere.

    I would turn on my PC for the day to work/game and when I get to the desktop everything loads fine but I'd click a browser and after minutes nothing opens, none of the programs would. I also can't type in search at bottom left.

    If I Windows + X that works and file explorer usually opens after time but thats all

    If I restart a few times eventually everything works as it should like it is now but I have no idea why its doing this, I have check for updates, run virus/malware scans and everything is completely fine.

    I am hoping maybe someone here can give me some insight on this issue

    Windows Version Number is: Version 2004 (OS Build 19041.329)
      My Computer


  2. Posts : 35,596
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #2

    Hi, please
    a. Perform a clean boot (Google or see tutorial if unsure how) and compare the outcome.
    b. Create a new user for test purposes. Log in as that user and compare the outcome.

    From an admin command or Powershell prompt run
    chkdsk c: /scan

    If ok similarly run
    SFC /SCANNOW

    Report the summary results.

    this issues started a couple days back
    Please examine your Update History. Is there an update corresponding to the date this started?

    When did you upgrade to build 2004?

    Thanks
      My Computers


  3. Posts : 7
    Windows 10 Home (OS Build 19041.329)
    Thread Starter
       #3

    dalchina said:
    Hi, please
    a. Perform a clean boot (Google or see tutorial if unsure how) and compare the outcome.
    b. Create a new user for test purposes. Log in as that user and compare the outcome.

    From an admin command or Powershell prompt run
    chkdsk c: /scan

    If ok similarly run
    SFC /SCANNOW

    Report the summary results.


    Please examine your Update History. Is there an update corresponding to the date this started?

    When did you upgrade to build 2004?

    Thanks
    I did the clean boot and had no issues going through everything and used another account and was fine as well, it seems hit or miss with the issue

    The chkdsk scan found no issues and neither did the SFC scan it said Windows Resource Protction did not find any integrity violations

    My last update was weeks before this issue so I feel it would be weird if it was that, the only thing near the date was the Microsoft Defender update but thats happened almost daily in my log since the 9th of June

    I am not sure how to know when I upgraded to build 2004?
      My Computer


  4. Posts : 35,596
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #4

    I did the clean boot and had no issues going through everything and used another account and was fine as well, it seems hit or miss with the issue
    That's a good sign- as is chkdsk passing and SFC.

    That everything was ok after a clean boot suggests that a startup is responsible for the problem.

    Either work back progressively from a clean boot state enabling things progressively to identify the problem, or from a normal boot, disabling things progressively, whichever is more convenient.

    If you have been receiving updates to 2004 during the period of interest, then the upgrade must have occurred before. I would have expected you'd have noticed the upgrade, as you'd have had to approve it if upgrading from 1909, and it would have taken perhaps an hour plus with 1 or more restarts.
      My Computers


  5. Posts : 7
    Windows 10 Home (OS Build 19041.329)
    Thread Starter
       #5

    dalchina said:
    That's a good sign- as is chkdsk passing and SFC.

    That everything was ok after a clean boot suggests that a startup is responsible for the problem.

    Either work back progressively from a clean boot state enabling things progressively to identify the problem, or from a normal boot, disabling things progressively, whichever is more convenient.

    If you have been receiving updates to 2004 during the period of interest, then the upgrade must have occurred before. I would have expected you'd have noticed the upgrade, as you'd have had to approve it if upgrading from 1909, and it would have taken perhaps an hour plus with 1 or more restarts.
    I see what you mean now, I think I upgraded to the 2004 like 2 weeks or so back

    Before hand I was running a much older version for a long time
      My Computer


  6. Posts : 35,596
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #6

    Ok, so not 2004 - related. As I suggested, time to work through your startups. Have you added or changed any?
      My Computers


  7. Posts : 7
    Windows 10 Home (OS Build 19041.329)
    Thread Starter
       #7

    dalchina said:
    Ok, so not 2004 - related. As I suggested, time to work through your startups. Have you added or changed any?
    I have almost everything disabled on my start ups already, the last two I just disabled ICUE and something else related to it. I literally only have Realtek HD Audio Manager as a start up enabled. Everything else on the list is disabled since not really that needed
      My Computer


  8. Posts : 35,596
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #8

    Please clarify: I read

    I did the clean boot and had no issues going through everything and used another account and was fine as well, it seems hit or miss with the issue
    meaning that after a clean boot you did not see the problem again.

    Does the last clause mean that both when logged in as a new user and after a clean boot you still see the same problem?
    Please state the situation clearly. Thanks.
      My Computers


  9. Posts : 7
    Windows 10 Home (OS Build 19041.329)
    Thread Starter
       #9

    dalchina said:
    Please clarify: I read



    meaning that after a clean boot you did not see the problem again.

    Does the last clause mean that both when logged in as a new user and after a clean boot you still see the same problem?
    Please state the situation clearly. Thanks.
    I have not seen the issue again since it worked this morning, it worked before and after a clean boot.

    The issue happened last couple days and after a few restarts it worked right, I posted the question after it was currently working.

    I guess I will have to wait and see if it happens again, I usually only boot up my PC once a day for work and then turn it off at night
      My Computer


  10. Posts : 35,596
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #10

    An erratic problem.. which at this point could be hardware, could be software. The most difficult.

    You can leave it in clean boot 'long enough' e.g. on overnight if that's relevant- if the problem recurs we know it's not related to basic startups.

    That takes patience. And if it doesn't recur, that's proof of nothing, unfortunately.

    You can boot your PC from a live boot disk- if the problem recurs, it's almost certainly not related to software.

    You can run hardware diagnostics - RAM tests, stress tests e.g. Driver Verifier (tutorials available), Prime 95.

    You can simplify hardware as much as possible - remove all but your system disk if you have more- remove the graphics card.

    You could inspect your Reliability History and see if there are reports corresponding to when you experienced the problem.

    You haven't stated the model of your PC. About how old is it? Did it first come with Win 10?

    Another possibility is a failing PSU.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:50.
Find Us




Windows 10 Forums