Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid 7.1.4 encounters a bug where a folder cannot be deleted

Featured Replies

In my virtual machine folder directory, there is a directory named Windows, which still cannot be deleted using the RM command. It prompts that it is occupied, but it is an empty folder. When I share this directory on Windows, it displays as messy code. After I delete it from Windows and refresh, it automatically appears again. What kind of folder is this? Why can't it be deleted? This problem has been bothering me for a long time. Shortly after I try some commands to force deletion, it will reappear.

333.png

ScreenShot_2025-10-14_150514_073.png

Solved by MAM59

  • Author

i think its a BUG

ScreenShot_2025-10-14_151235_089.png

  • Community Expert

Check filesystem on the cache.

  • Author
38 minutes ago, Kilrah said:

Check filesystem on the cache.

Is this normal?

ScreenShot_2025-10-14_162558_931.png

  • Community Expert
  • Solution

yes, this is normal if you ever updated UNRAID from early ZFS to current one.

You need to do "zpool update" once (will be necessary for further versions too maybe, so keep an eye open).

BUT BEWARE! once done, you cannot go back to older versions of UNRAID anymore! The disks will not be readable then!!!

On the other hand, this is only an INFO, it just says: "there are new features available that are currentlic not enabled yet, waiting for your approval."

You can also ignore it for the next decades, but of course, you will not get any benefit from the new features anymore too.

What HAS changed should be documented somewhere, you may compare the output of zpool-features on an "old" and a "new" filesystem and then decide if you want it or not.

But if you never plan to downgrade UNRAID, just do it and dont think about it.

  • Author
On 10/14/2025 at 5:30 PM, MAM59 said:

yes, this is normal if you ever updated UNRAID from early ZFS to current one.

You need to do "zpool update" once (will be necessary for further versions too maybe, so keep an eye open).

BUT BEWARE! once done, you cannot go back to older versions of UNRAID anymore! The disks will not be readable then!!!

On the other hand, this is only an INFO, it just says: "there are new features available that are currentlic not enabled yet, waiting for your approval."

You can also ignore it for the next decades, but of course, you will not get any benefit from the new features anymore too.

What HAS changed should be documented somewhere, you may compare the output of zpool-features on an "old" and a "new" filesystem and then decide if you want it or not.

But if you never plan to downgrade UNRAID, just do it and dont think about it.

Thank you very much, but the extra "Windows" folder still cannot be deleted

  • Community Expert
56 minutes ago, Gaeroce said:

Thank you very much, but the extra "Windows" folder still cannot be deleted

You seem to have (or had) a VM named "Windows". Stop VMs, remove the VM "Windows" and the Folder will go away too.

  • Author
2 hours ago, MAM59 said:

You seem to have (or had) a VM named "Windows". Stop VMs, remove the VM "Windows" and the Folder will go away too.

I created a virtual machine named "Windows" some time ago. However, I deleted it shortly after. Nevertheless, the folder persisted and remained undeleted. Currently, I only have one virtual machine named "Windows 11 IoT LTSC".

  • Author

The folder named "Windows" cannot be deleted normally. It has been bothering me for a long time, by the way. There is a space after this folder name. It should be "Windows " or "Windows\"

ScreenShot_2025-10-16_141221_365.png

ScreenShot_2025-10-16_141230_705.png

  • Community Expert

try to rename it from the shell or with mc.

(and sorry, my chinese does not really exist, your screenshots do not help me at all :-( )

  • Author
18 hours ago, MAM59 said:

try to rename it from the shell or with mc.

(and sorry, my chinese does not really exist, your screenshots do not help me at all :-( )

OK,Let me try again

  • Author

I have found this information. How can I completely delete it

ScreenShot_2025-10-14_162558_931.png

  • Author

I think I've found the crux of the problem. When I run the virtual machine named "Windows 11 IoT LTSC", it automatically creates a folder named "Windows" shortly after. When my virtual machine is running, it cannot be deleted. However, when I close the virtual machine, it can be deleted normally

ScreenShot_2025-10-14_162558_931.png

  • Author
2 minutes ago, Gaeroce said:

I think I've found the crux of the problem. When I run the virtual machine named "Windows 11 IoT LTSC", it automatically creates a folder named "Windows" shortly after. When my virtual machine is running, it cannot be deleted. However, when I close the virtual machine, it can be deleted normally

ScreenShot_2025-10-14_162558_931.png

By the way, my unRiad only has an integrated graphics card and hasn't installed a discrete graphics card, so I used the Intel GVT-g plugin. I'm not sure if it's related to this plugin

  • Community Expert
1 hour ago, Gaeroce said:

When I run the virtual machine named "Windows 11 IoT LTSC", it automatically creates a folder named "Windows" shortly after

Then check the settings for that VM. Most likely you have defined an "additional folder named Windows" there. Either correct or delete that setting. Look for "extra path" or something alike. (cannot look myself, no VMs here)

Edited by MAM59

  • Author
47 minutes ago, MAM59 said:

Then check the settings for that VM. Most likely you have defined an "additional folder named Windows" there. Either correct or delete that setting. Look for "extra path" or something alike. (cannot look myself, no VMs here)

Please wait a moment.

  • Author
48 minutes ago, MAM59 said:

Then check the settings for that VM. Most likely you have defined an "additional folder named Windows" there. Either correct or delete that setting. Look for "extra path" or something alike. (cannot look myself, no VMs here)

<?xml version='1.0' encoding='UTF-8'?>

<domain type='kvm' id='4'>

<name>Windows 11 IoT LTSC</name>

<uuid>b985c644-63bb-f512-8c43-2edb5114bf6f</uuid>

<metadata>

<vmtemplate xmlns="http://unraid" name="Windows 11" icon="windows11.png" os="windowstpm" webui="" storage="default"/>

</metadata>

<memory unit='KiB'>16777216</memory>

<currentMemory unit='KiB'>16777216</currentMemory>

<memoryBacking>

<nosharepages/>

</memoryBacking>

<vcpu placement='static'>6</vcpu>

<cputune>

<vcpupin vcpu='0' cpuset='3'/>

<vcpupin vcpu='1' cpuset='9'/>

<vcpupin vcpu='2' cpuset='4'/>

<vcpupin vcpu='3' cpuset='10'/>

<vcpupin vcpu='4' cpuset='5'/>

<vcpupin vcpu='5' cpuset='11'/>

</cputune>

<resource>

<partition>/machine</partition>

</resource>

<os>

<type arch='x86_64' machine='pc-i440fx-9.1'>hvm</type>

<loader readonly='yes' type='pflash' format='raw'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader>

<nvram format='raw'>/etc/libvirt/qemu/nvram/b985c644-63bb-f512-8c43-2edb5114bf6f_VARS-pure-efi-tpm.fd</nvram>

</os>

<features>

<acpi/>

<apic/>

<hyperv mode='custom'>

<relaxed state='on'/>

<vapic state='on'/>

<spinlocks state='on' retries='8191'/>

<vpindex state='on'/>

<synic state='on'/>

<stimer state='on'/>

<vendor_id state='on' value='none'/>

</hyperv>

</features>

<cpu mode='host-passthrough' check='none' migratable='on'>

<topology sockets='1' dies='1' clusters='1' cores='3' threads='2'/>

<cache mode='passthrough'/>

<feature policy='disable' name='hypervisor'/>

</cpu>

<clock offset='localtime'>

<timer name='hpet' present='no'/>

<timer name='hypervclock' present='yes'/>

</clock>

<on_poweroff>destroy</on_poweroff>

<on_reboot>restart</on_reboot>

<on_crash>restart</on_crash>

<devices>

<emulator>/usr/local/sbin/qemu</emulator>

<disk type='file' device='cdrom'>

<driver name='qemu'/>

<target dev='hda' bus='sata'/>

<readonly/>

<boot order='2'/>

<alias name='sata0-0-0'/>

<address type='drive' controller='0' bus='0' target='0' unit='0'/>

</disk>

<disk type='file' device='cdrom'>

<driver name='qemu'/>

<target dev='hdb' bus='sata'/>

<readonly/>

<alias name='sata0-0-1'/>

<address type='drive' controller='0' bus='0' target='0' unit='1'/>

</disk>

<disk type='file' device='disk'>

<driver name='qemu' type='raw' cache='writeback' discard='unmap'/>

<source file='/mnt/user/domains/Windows 11 IoT LTSC/vdisk1.img' index='1'/>

<backingStore/>

<target dev='hdc' bus='sata' rotation_rate='1'/>

<serial>vdisk1</serial>

<boot order='1'/>

<alias name='sata0-0-2'/>

<address type='drive' controller='0' bus='0' target='0' unit='2'/>

</disk>

<controller type='pci' index='0' model='pci-root'>

<alias name='pci.0'/>

</controller>

<controller type='sata' index='0'>

<alias name='sata0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

</controller>

<controller type='virtio-serial' index='0'>

<alias name='virtio-serial0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>

</controller>

<controller type='usb' index='0' model='ich9-ehci1'>

<alias name='usb'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>

</controller>

<controller type='usb' index='0' model='ich9-uhci1'>

<alias name='usb'/>

<master startport='0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>

</controller>

<controller type='usb' index='0' model='ich9-uhci2'>

<alias name='usb'/>

<master startport='2'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>

</controller>

<controller type='usb' index='0' model='ich9-uhci3'>

<alias name='usb'/>

<master startport='4'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>

</controller>

<interface type='bridge'>

<mac address='52:54:00:01:b4:de'/>

<source bridge='br0'/>

<target dev='vnet3'/>

<model type='virtio-net'/>

<alias name='net0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>

</interface>

<serial type='pty'>

<source path='/dev/pts/1'/>

<target type='isa-serial' port='0'>

<model name='isa-serial'/>

</target>

<alias name='serial0'/>

</serial>

<console type='pty' tty='/dev/pts/1'>

<source path='/dev/pts/1'/>

<target type='serial' port='0'/>

<alias name='serial0'/>

</console>

<channel type='unix'>

<source mode='bind' path='/run/libvirt/qemu/channel/4-Windows 11 IoT LTSC/org.qemu.guest_agent.0'/>

<target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>

<alias name='channel0'/>

<address type='virtio-serial' controller='0' bus='0' port='1'/>

</channel>

<input type='mouse' bus='ps2'>

<alias name='input0'/>

</input>

<input type='keyboard' bus='ps2'>

<alias name='input1'/>

</input>

<tpm model='tpm-tis'>

<backend type='emulator' version='2.0' persistent_state='yes'/>

<alias name='tpm0'/>

</tpm>

<sound model='ich9'>

<alias name='sound0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>

</sound>

<audio id='1' type='none'/>

<hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci' display='off'>

<source>

<address uuid='78f53dc2-b7d1-44ca-a94e-104da680659a'/>

</source>

<alias name='hostdev0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>

</hostdev>

<memballoon model='virtio'>

<alias name='balloon0'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

</memballoon>

</devices>

<seclabel type='dynamic' model='dac' relabel='yes'>

<label>+0:+100</label>

<imagelabel>+0:+100</imagelabel>

</seclabel>

</domain>

  • Community Expert
12 minutes ago, Gaeroce said:

<vmtemplate xmlns="http://unraid" name="Windows 11" icon="windows11.png" os="windowstpm" webui="" storage="default"/>

I guess, it is this line, try to change it to your "Windows 11 IoT LTSC" and see what happens.

(just a guess!!! but I think the change is harmless)

Maybe a leftover from your former rename action ?

  • Community Expert
4 hours ago, Gaeroce said:

I have found this information. How can I completely delete it

Is the pool zfs? If yes, it may be a dataset, post the output from zfs list -t all

  • Author
19 hours ago, JorgeB said:

Is the pool zfs? If yes, it may be a dataset, post the output from zfs list -t all

Yes,ZFS.But this issue seems to have been resolved. After I shut down the virtual machine, it could be deleted directly. It has been two days, and it hasn't reappeared.

  • Author

Oh, this is a terrible thing. This folder has reappeared. When I close the VM (Virtual Machine), it cannot be deleted anymore

  • Community Expert

you might consider to install the plugin "open files".

With it (and after scanning a looooooooooooooooong list...) you might be able to determine which process is holding "Windows" open (and therefor locking it against deletion).

But be prepared that the plugin needs some skills to interpret the data (and setting a filter to just view the correct stuff, there are thousands of files open all the time)

Once you found the culprit, the people here might tell you how to avoid it.

  • Author
35 minutes ago, MAM59 said:

you might consider to install the plugin "open files".

With it (and after scanning a looooooooooooooooong list...) you might be able to determine which process is holding "Windows" open (and therefor locking it against deletion).

But be prepared that the plugin needs some skills to interpret the data (and setting a filter to just view the correct stuff, there are thousands of files open all the time)

Once you found the culprit, the people here might tell you how to avoid it.

OK.Let me try

  • Author
40 minutes ago, MAM59 said:

you might consider to install the plugin "open files".

With it (and after scanning a looooooooooooooooong list...) you might be able to determine which process is holding "Windows" open (and therefor locking it against deletion).

But be prepared that the plugin needs some skills to interpret the data (and setting a filter to just view the correct stuff, there are thousands of files open all the time)

Once you found the culprit, the people here might tell you how to avoid it.

I downloaded the "open files" plugin, but I didn't find any occupation related to the "Windows" folder in the list. It's quite strange

44444.png

  • Community Expert

Too bad, but as i said, the plugin is not easy to use...

click on "search" in the last column and enter the full path of the file you are looking for

like /mnt/cache/domains/Windows

Also, you might check if the Windows Folder still contains a file.

I also have a "ghost" here:

grafik.png

This VM does not exist anymore (actually I have NO VMs here anymore)

but the last Stamp for running was not deleted automatically.

(but I can delete it because no VM service is currently activated)

Anyway, my educated guess would be:

  • you once had a VM named "Windows"

  • some day you have changed the name to "Windows 11 24H2-lts" or something

  • the rename worked mostly but somewhere in the VMs config or image file is still a reference to "Windows"

Besides making you upset, I dont think, it will do any harm, maybe you just can live with it?

BTW: it would be nice if you could switch your UNRAID to "english" before you take screenshots. My (and I guess a lot of other people here too) chinese is not that fluent, I always have to guess where in the GUI the shot was taken from. Could speed up things and avoid confusion. (you can switch back after the shot)

Edited by MAM59

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.