Cleaninstall 18363.449 - $WINRE_BACKUP_PARTITION.MARKER - why?


  1. Posts : 481
    Windows 10 Pro
       #1

    Cleaninstall 18363.449 - $WINRE_BACKUP_PARTITION.MARKER - why?


    Hello.
    Cleaninstalled 18363.449 some days ago, and got a strange file, that gave an error at every reboot. I could not delete the file nor rename it. I gave up and did a new cleaninstall of same version. Now the file is back (again at 0 bytes), but this time it has only cost an error twice. Most of the time it just "is there". I still can't delete it. The name of the file is $WINRE_BACKUP_PARTITION.MARKER

    I have tried to google it, but that did not help, as all I found was an explanation of this being from "Windows Recovery" ?!?! But this is not a "recovery" it is a clean install. The owner (in properties) is SYSTEM, and the Administrator (me) is not allowed to delete or rename it. I have tried to search for it in reg.database to find out when (or where) the startup-error with this file is comming from. But no succes.

    How do I delete this file?
      My Computer


  2. Posts : 4,224
    Windows 10
       #2

    Check out this superuser thread: windows - What is this file $WINRE_BACKUP_PARTITION.MARKER - Super User. You can boot to alternate media (bootable installer, or a repair disk like Kyhi's Rescue Disk) and delete it at the command line easily. I've done so myself on at least a couple of systems with no obvious ill effects.
    HTH,
    --Ed--
      My Computers


  3. Posts : 25,052
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #3

    Burgurne said:
    Clean installed 18363.449 some days ago, and got a strange file ... $WINRE_BACKUP_PARTITION.MARKER
    ...I have tried to google it, but that did not help, as all I found was an explanation of this being from "Windows Recovery" ?!?! But this is not a "recovery" it is a clean install....

    I have seen that file C:\$WINRE_BACKUP_PARTITION.MARKER on a few systems. The common factor is that they have no Recovery partition, but the WinRE environment (Advanced Startup) is still available and fully functional. This is because, instead of installing it in its own separate partition, Setup has put the windows image file Winre.wim that is used to boot to Advanced Setup in the hidden system folder C:\Recovery.

    I understand that since 1903 the default for a clean install is NOT to create a separate Recovery partition but to put the recovery environment on the same partition as the Windows system, ie the C: drive.

    $WINRE_BACKUP_PARTITION has an extension of .MARKER, and it's sole purpose seems to be to indicate that the C: drive is the partition that holds the WinRE boot files. The file is owned by SYSTEM.
      My Computers


  4. Posts : 25,052
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #4

    EdTittel said:
    Check out this superuser thread...
    Your link agrees with my observations, saying: "...I have seen this on a variety of machines, all of which had Windows 10 installed as a single partition with no recovery."

    My test machine (System Two) has no Recovery partition, but it can still boot to the recovery environment as the recovery boot files are on its C: partition.
      My Computers


  5. Posts : 25,685
    Windows 11 Pro 22621.160
       #5

    I have legacy bios so I do not have that..
      My Computer


  6. Posts : 481
    Windows 10 Pro
    Thread Starter
       #6

    Well, I don't have the file winre.wim in Recovery (or anyother place) The Recovery folder is there as a hidden folder, but it is empty. Maybe this is the reason for the errors that comes once in a while??
    I booted from Acronis rescue disk, and deleted it. So far no errors at all at boot into Windows
      My Computer


  7. Posts : 25,052
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #7

    Josey Wales said:
    I have legacy bios so I do not have that..
    It doesn't seem to matter if it is Legacy or UEFI, my test machine is a legacy bios MBR system. What seems to matter is whether or not setup created a recovery partition. If you have one you shouldn't have this marker file on C:.
      My Computers


  8. Posts : 25,685
    Windows 11 Pro 22621.160
       #8

    Bree said:
    It doesn't seem to matter if it is Legacy or UEFI, my test machine is a legacy bios MBR system. What seems to matter is whether or not setup created a recovery partition. If you have one you shouldn't have this marker file on C:.
    I do not have one but when I was in The Fast Ring it created one. I had two recovery partitions and MR changed to WinRe from WinPE
      My Computer


 

  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 16:44.
Find Us




Windows 10 Forums