Cannot delete system files created from Windows 10 Media Creation Tool

Page 5 of 7 FirstFirst ... 34567 LastLast

  1. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #41

    The diagram you posted above about needing permission from your normal user account indicates that your normal account is still the owner of the bin folder.

    While you are in the PowerRun System/TrustedInstaller you should be able to take ownership of that account for the System/TrustedInstaller. The instructions are, I think, in a previous page of this thread.

    I have not used the PowerRun UI. If you have opened a command prompt window using it then the commands I gave you apply whatever current folder you are in.
    - You do not need to change to the downloads folder in the command prompt window to use that command.
    - All you need to do is check [in your normal File explorer or otherwise] what the full path to that bin folder is.

    [I am having great trouble posting. It is taking 3 or 4 attempts each time. f14tomcat has far greater experience of this utility than I have so you should rely on his advice if it conflicts in any way with mine.]

    I have to log off now, best of luck,

    Denis
      My Computer


  2. Posts : 23
    Windows 10
    Thread Starter
       #42

    Try3 said:
    Matthew,

    If you want some reassurance that you have higher status using a cmd window within PowerRun then open a command prompt within it and enter
    whoami

    Attachment 240902

    Note - I have not yet tried the advice on the PowerRun webpage to use TrustedInstaller status but I assume that if I did the result would also be shown in response to whoami.

    Denis

    Interesting. When I do this via PowerRun I get the following:


    Cannot delete system files created from Windows 10 Media Creation Tool-screenshot-11-.png
      My Computer


  3. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #43

    shingdao said:
    Interesting. When I do this via PowerRun I get the following:


    Cannot delete system files created from Windows 10 Media Creation Tool-screenshot-11-.png
    There are 2 .exe for PowerRun. x86 and x64. Which are you running? I get

    Cannot delete system files created from Windows 10 Media Creation Tool-2019-07-21_20h25_09.pngCannot delete system files created from Windows 10 Media Creation Tool-2019-07-21_20h24_03.png

    And the default for starting is as TrustedInstaller.
      My Computers


  4. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #44

    I just noticed you are running 17134. That's 1803 from April of last year.

    I, too, need to sign off. Getting late here.
      My Computers


  5. Posts : 23
    Windows 10
    Thread Starter
       #45

    f14tomcat said:
    I just noticed something in your pic. You only have 1 Explorer running. One. When I do the same thing, I have 2. The one that was running, and the new one started under PowerRun. Verify again that you actually did run it in PowerRun. There should be 2 instances.

    Attachment 240899
    There is only one instance of explorer.exe when going through PowerRun.
      My Computer


  6. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #46

    There are log collectors used in another forum room.
    Run both V2 and DM and upload results into this thread:
    BSOD - Posting Instructions
      My Computer


  7. Posts : 23
    Windows 10
    Thread Starter
       #47

    f14tomcat said:
    I just noticed you are running 17134. That's 1803 from April of last year.

    I, too, need to sign off. Getting late here.
    Alright, thanks for your help!

    - - - Updated - - -

    f14tomcat said:
    There are 2 .exe for PowerRun. x86 and x64. Which are you running? I get

    Cannot delete system files created from Windows 10 Media Creation Tool-2019-07-21_20h25_09.pngCannot delete system files created from Windows 10 Media Creation Tool-2019-07-21_20h24_03.png

    And the default for starting is as TrustedInstaller.
    Version x64. Confirm default is TrustedInstaller.

    - - - Updated - - -

    f14tomcat said:
    I just noticed you are running 17134. That's 1803 from April of last year.

    I, too, need to sign off. Getting late here.
    I didn't realize it was such an old version. Windows Update is not working properly so I usually have to download updates manually but it should at least have given me a notice that a new version is available. I'll try to update manually.
      My Computer


  8. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #48

    Matthew,

    When the bin problem is combined with "Windows Update is not working properly" and that different response you are getting to PowerRun-Cmd-WhoAmI, it makes me think you need to do a clean install.
    Clean Install Windows 10 - TenForumsTutorial

    I appreciate that this can involve a lot of work
    [making a system image beforehand]
    [testing your boot disk beforehand to make sure you can boot up in order to restore that system image]
    [backing up all your own files beforehand]
    [installing your applications afterwards]
    [setting up the OS afterwards]
    [setting up the the applications afterwards]

    If there is any other solution I would now hazard the guess, based on what has been reported in this thread, that it will come out of following zbook's guidance about BSOD - Posting instructions.

    Denis
      My Computer


  9. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #49

    My post #37 [on page 4] about deleting a folder using Del & RD had errors which I have now corrected.

    Denis
      My Computer


  10. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #50

    Try3 said:
    Matthew,

    When the bin problem is combined with "Windows Update is not working properly" and that different response you are getting to PowerRun-Cmd-WhoAmI, it makes me think you need to do a clean install.
    Clean Install Windows 10 - TenForumsTutorial

    I appreciate that this can involve a lot of work
    [making a system image beforehand]
    [testing your boot disk beforehand to make sure you can boot up in order to restore that system image]
    [backing up all your own files beforehand]
    [installing your applications afterwards]
    [setting up the OS afterwards]
    [setting up the the applications afterwards]

    If there is any other solution I would now hazard the guess, based on what has been reported in this thread, that it will come out of following zbook's guidance about BSOD - Posting instructions.

    Denis
    Matthew and Denis. As more pieces come together, I'm also of the mind that a clean install is in order. These issues tend to snowball after a while, and for you, Matthew, it's been a while. Too many things just don't smell quite right. You could continue chasing this down for days and not be any better off, or backup all your personal data (not the bin stuff.....), wipe all partitions of the OS, and start with a clean install. 1903, not 1803. Denis posted the tutorial link. Help with any parts of it are just a post away.

    May be your best solution at this point.

    ---------------------------------------------------------------------------------------------------------------------------------------

    The fact you only have 1 Explorer running when there should be 2, and the Whoami not reporting "NT Authority" makes me believe the PowerRun Explorer never actually started. Which makes me believe there are permission issues with your account preventing running anything higher than Administrators Group. We could dig thru the Event Logs to verify, but it all seems to point to a clean install is in order.
    Last edited by f14tomcat; 22 Jul 2019 at 04:45. Reason: Additional comments
      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 08:26.
Find Us




Windows 10 Forums