onyxdrew

I updated to 6.11.1 since it mentioned it put back SMBv1 but doesn't seem to have made any difference as far as authenticating with @ user.

I thought I would provide a quick update. I ditched my AMD rig; 5700G + 5500XT, and replaced it with Intel i5 12400 + 1050ti. Plex natively supports intel apu and it worked without any drivers or effort at all, just pass device and turn it on. It seems plenty powerful. I also was able to pass my 1050ti into a VM with zero issues, no need to extract BIOS or anythign fancy. I even have it working with UNRAID 6.11 and Windows 11 with TPM. It was crazy how easy this just worked, with all the pain I had with AMD rig. The AMD stuff was more power efficient, but honestly worth the trade off. I know this isn't overly helpful here, but know that this AMD + APU stuff is probably just not even worth the effort. The performance was not good, and overall nothing just works on this platform. Happy unraider now unsubscribing.

not arguing that, but it literally worked on every version of unraid til 6.11, and works well on my other network appliances which are also based on linux (QNAP/Synology).

I don't "need" it to work. I just don't want to have to mess with having a different credential. Up until version 6.11 I could just log into any of my many pc's and access shares without having to worry about user/passwords. It would just pass it along and everything works.

Ah yes.. I have tried clearing the credentials in windows as well. That did not impact my access. My case is also different in that my users all work, except the one with an @ in the username (email address, aka microsoft account). I cannot even type that @ sign user into windows and have it work, but all my users that don't have an @ sign do work. I also have multiple desktops/laptops with Win10/11 and none of the ones logged into microsoft account work. The ones logged in locally do. Very odd. I tried the NTLM and SMB version tags in this thread as well, also don't seem to work:

Like mentioned in my first posts, I have users created. I can even connect as long as I use the one that isn't an email address. I had to add the email address user following the steps in the post I linked, where you add a user, and rename it manually, due to the @ sign.

Looking at other threads, this isn't related to browsing to the server. I can see it fine in list of devices under network, I can use UNC path \\servername as well as \\servername.local to get a list of shares, and same goes for \\IP. When I click any share, I get prompted for user/pass now though, and it fails with my email based user, which matches my microsoft account email address. I also tried resetting the password under users in unraid, nothing. I tried editing user permissions to one share to see if that would help, nothing. I reviewed other threads, and all the settings I could find for SMB and nothing.

I created the email based username using the process outlined here:

Hoping I missed something simple. I have multiple machines running Win10 and Win11 that all log into the same Microsoft account. This was working in 6.10.x, but not after upgrading to 6.11. I can connect fine when prompted for user/pass, I type in a none email based user/pass combo. I would rather not have to save credentials and the core credentials from the machine should be sufficient.

Yeah when I was screwing around my system reset the cmos settings as one time I locked it up... I had thought I had saved teh profile but it doesn't appear to have worked. I'm burned out of it for now, will pick it up again next week maybe. Not sure why the updated QEMU would have much impact either?

No output, updated driver with Windows Update instead of downloading from AMD.com... back to good-ole error 43

Just installed windows fresh again to be sure, and here it is after all the Windows updates:

Next step woudl be revert my USB stick back to 6.9.2, I did take a backup... see if it truly would just work again with that version of QEMU/etc.

Yeah, my point is that you never got output, and maybe never used the version of the driver I was using? Not sure if I ever got the bios messages/etc or if the VM would only display after it got Windows started, I never paid attention to that. No, it showed up as the same AMD device the whole time. I noticed It was good to go in Device Manager right before I installed driver. I might start over and not install any driver and see what it does.

I wonder if its related to the AMD GPU drivers? I downloaded the latest, you might have as well, maybe I was on a slightly older version before? The GPU only shows error 43 after driver install.