JustinChase

No, because I'd already rolled back before I saw that image. I rebooted the laptop about 4 times while I was running 6.12.2 and they never worked, and I could not re-map a drive makes sense. How would you recommend one begins this update to their security? I'm not in love with SMB, it's just what i setup long ago, and has mostly worked fine for me. I don't open any ports to the internet, (I run a ShieldsUp test regularly) and I'm not really worried about anyone on my wifi, so I'm not sure it's "necessary", but more security is usually good. Thanks all for the help

I reverted to 6.12.0 and upon unraid server restarting (not my laptop), shares were instantly available with no further input from me. I guess this is, once again, a formal bug report and no longer a request for help. my system did no change, only the unraid version. this points to unraid issue, not a me issue. thanks again for trying to help

thank you, I appreciate the data point. I have used the server name on multiple computers for over a decade without issue. Even if it were unreliable, that is still an error and should be fixed. But, in my case that has not been the case, and it has worked just fine. With all that said, I have tried to connect with the IP address and that also fails. Windows sees the server name just fine, but refuses to connect.

Thanks for the help. it's not a company laptop. it has worked mostly flawlessly this way for a decade. it's just the latest upgrade of unraid that has caused the issue. i did not change anything on the laptop. as I posted before, a previous upgrade caused the same issue, and reverting instantly restored full functionality. I have not reverted simply because I'm hoping there are some actual troubleshooting steps I can take. i will wait until after the US holiday and create a new post in general if there isn't any more feedback here.

I've been able to use name for about a decade without issue. However, i did try using IP address, and it still fails to connect. There is something about this new version that breaks the ability to map network drives on my laptop. The diagnostics file I attached previously doesn't tell me anything, but I also don't really know what to look for. What else can i do to help diagnose/troubleshoot/solve this issue?

Sorry, I was mistaken in the versions that had the issues. I had version 6.12.0-rc5 installed and mapped drives worked fine. I updated to version 6.12.0-rc6 lost mapped drives. I downgraded back to rc5 and it all worked again. Earlier today I updated to 6.12.0 and tested mapped drives and it all looked fine. I then updated to 6.12.2 and lost mapped drives again. I have tried re-mapping, but it does not work. Windows tells me it cannot access \\MEDIA (the name of my server). Windows does find it under network, but refuses to connect to it. Diagnose does not find any issues.

windows 11 shares are broken in this build. I was on 6.11.5 (I think) and updated to 6.11.7 (can't remember exactly which, but not 6.12) and I lost the ability to open/use mapped drives in windows explorer. After a couple hours trying to resolve, I thought to just roll back to 6.11.5 and mapped drives worked again. Earlier today, i saw that 6.12.2 was available, but I could only update to 6.12, which I did. i tested mapped drives and all seemed fine. Then I updated to 6.12.2 and now mapped drives do not work again. I'm guessing this is me not changing some setting, or this would have probably been reported before, but either way, it IS broken for me, and I don't know how to resolve it. Diagnostics attached, help much appreciated. media-diagnostics-20230704-1710.zip

I recently update to the newest release candidate (Version: 6.12.0-rc2) I setup a windows VM and used the auto setting for disk location, which created a directory on the cache drive with the same name as the VM name. I'd set it to be 65G in size. I got it all setup and running. I later realized this new directory was not setup to use the cache drive, so the fix common problems plugin threw an error about this. I already had a directory on the cache for VM images, so I just moved the image from the one "auto" created location and changed the name to reflect the VM it is used for. i.e. I changed it from cache/windows11/vdisk1.img to cache/VMs/Media Server/windows11.img I then updated the VM to point to this new location. I then discovered that this changed resulted in the VM going from 65G to 30G and is now unable to be changed back to 65G. This also resulted in the VM not starting. I'm guessing because it expects a different size than the new size. 1. Is this recoverable from here, or do I need to pull a backup of the VM from yesterday and edit the VM back to use the auto location? 2. Is this a bug, or is this expected behavior? If expected, why?

I never found a solution. I ended up just creating a new VM and installing windows from scratch. I only used mine for a media player, so setting it up from scratch seemed like it would take less time than I was spending trying (so very unsuccessfully) to fix this issue. I actually reinstalled windows in place over the existing version, thinking it would fix any issues, but it had no positive effect. I hope you find a solution, but I have given up and just have a new VM now.

funnily enough, I was just about to do that when I saw this. Yes, that worked. not sure why the whole controller being passed thru no longer works, but considering how much time I've lost to this stupid computer situation, I'm going to call it "good enough" for a while. i'd still love to figure out why it seems the entire VM seems to be running as if the CPU has been replaced with a 25 year old pentium, but again, another day. Thanks for your help

The posts show, but the first one listed has the yellow triangle. I can update the driver for it, but the triangle comes back eventually. I can delete it, but upon restart it comes back. I suspect one of the folders in the virtio disk has the correct driver, but I think I've tried pointing to every main folder, drilling down to the w11/amd64 folder, but none have worked. The really weird thing is that the windows install that was working, but just really, REALLY slow now also does not work for this USB. So, I don't have a keyboard or mouse, so I'm trying to do everything via remote desktop. I really just wanted to 'fix' the otherwise working windows, but that hasn't worked, and installing a new machine also isn't working, and I'm just spending way, way too much time trying to get what used to work working again. Some days i really do hate computers!

Yes, recreating the VM from scratch and pointing to the existing image did work, thank you. Sadly, I cannot get the USB passthru to work in either the old/slow/borked image, nor in the newly created, installed from iso windows install. I have both VM's running as Q35-7.1 machines, thinking this is newer and allows for PCIe, but maybe this is the issue with the USB3 controller. Anyone know if USB3 can/should work in a Q35 VM, or if there is some other trick I'm missing? This is the same controller that used to work before I ran into the borked/slow windows issue, so I know if can/should work. Thank you for acknowledging and fixing this issue!

Sadly, the root of my issue is that the existing windows install is borked and I cannot figure out what is wrong, and I've spent too much time trying to find an answer. I've posted here a few times asking for help, but have not gotten any help to get it working properly again, so I decided to just start fresh (thinking it would save me time; it has not!) The real issue is that the VM setup has just simply removed the network setting part. There is literally no network setting provided to change. I could probably figure out how to add them with the XML, but i really don't want to have to dive that deep to fix what i think is just a bug in unraid.

The issue I'm having is with network adapter. When creating a new Win 11 VM, windows doesn't find a network adapter, so you just can't proceed.. I tried selecting e1000 as the adapter, but that didn't work. I then had to select the accessibility options in the windows setup BEFORE getting to the 'no network' scree, since you cannot access the on-screen keyboard at that point. Once i had that turned on, I could then get the command prompt, then type something (oobd/netpasssomething - i don't have it in front of me now), to bypass the force network issue, so I could get the windows installation to finish. But, I do not have a network adapter in windows now. The troubleshooter doesn't even find an adapter, so I figured I'd have to change it in the VM setup, but network is not even shown in the VM setting page now, so I can't even try changing the adapter to see if I can get that to force an adapter into this windows install. I cannot find a current 'how to install windows 11 VM' guide where any of this is covered, and I'm stuck at this point, and ready to just give up on having a working windows 11 install. I used to have one working, but it began working at about 1/10th speed, and I could not find any help in resolving that, so I figured just reinstalling windows would be faster, but this network thing is just killing me. How can I get a working network inside a brand new Windows 11 VM?

Does anyone have any suggestions on how to begin troubleshooting this? Log files don't show me much, but I don't really know what to look for. This same hardware worked fine for a very long time. I can't think of anything I've done recently to change the setup, other than change the DNS settings of unraid to cloud9, but I have since removed this change and have unraid just using the router for DNS right now. This didn't help. It just feels like the processor got changed to a Pentium from 1990, everything is just really, really slow.