Uniti Core disappeared from Win 11 PC

I am hoping someone will be able to help me here.

I updated my PC to the new, 2024, version of Windows 11 on Sunday. All went smoothly & well except for one thing. My Uniti Core has disappeared from Windows File Explorer & I can’t get it added back. It automatically added itself to my previous Windows 10 & Windows 11 versions. It appeared & I could add or delete items from the Downloads folder at will.

I have been trying to add it back by using the ‘Map Network Drive’ command but am thwarted by the pop up box that appears prompting me to ‘enter my Networking Credentials’. It pre-populates it with my email address & asks for a password.

I have no idea what this password maybe & don’t recall ever being asked for one before or ever creating one. Many internet searches to find the password &/or sort the problem have proved fruitless.

I carefully record all my passwords & have spent a delightful afternoon entering everyone I can find with no success.

I think there are a few computer wizards here & am hoping that one of you will be kind enough to help me add my Core back to my PCs network. Please note that the Core is showing as normal in my routers list of network devices.

1 Like

Is your windows 11 PC connected to your network with WiFi? If so try it with Ethernet. That solved it for me. There was another thread about this, but basically the 2024/H2 update to windows 11 doesn’t allow connection to wireless network resources that don’t require credentials. But Ethernet is ok, for the time being anyway.

(The Core is Ethernet connected of course, but the WiFi connection to the PC means the PC OS disallows the connection.)

You can re-enable insecure guest logins via group policy.

Since MS are moving this way will we see a Core firmware which adds (optional) simple username/password to the Downloads folder?

Oh, that’s easy then, obvious even……… :face_with_open_eyes_and_hand_over_mouth:.

OK, I’m getting my coat as I type :innocent:.

ATB, J

You try to access directly from “Map” ?

This worked for me. Set Insecure guest authentication to enabled

and: disable digitally sign communications …

  1. Open the Local Group Policy Editor (gpedit.msc) on your Windows device.
  2. In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.
  3. Double-click Microsoft network client: Digitally sign communications (always).
  4. Select Disabled > OK.

See more background info on https://techcommunity.microsoft.com/blog/filecab/smb-signing-and-guest-authentication/3846679

@davidhendon @Wditters @IainO

Thanks to you all for your help.

A couple of hours further internet searching finally took me to the ‘enable insecure guest logins’ solution (as per @IainO suggestion), which worked first time.

Had no idea this was causing the problem &, without web help, would have had no idea what to do.

I did not do anything with previous Win 10 & all earlier Win 11 versions, Core was accessible by default as far as I am aware. Presumably, Win 11 2024 ver. has been configured differently in the default installation.

Not too concerned about the word ‘insecure’ regarding guest access as I presume MS would not have allowed it if there was a major risk. However, I will drop a line to Naim for their view & will mention Iain’s suggestion of a password type solution to access the Downloads folder.

Again, thanks to all for your help.

1 Like

Note: You might still run into the Digitally Sign Communications parameter further down the road. I am running a Windows Insider build in DEV which is newer than the regular releases. I run that on a Snapdragon laptop …

In my case merely enabling Unauthenticated Guest Access was not sufficient… My connection to the Core only started working again after disabling Digitally Signed Communications … And that was almost immediately out of the box on a fresh Windows Insider install

1 Like

I have emailed Naim about this & will post their reply here if I receive one.

1 Like

I’ll be interested to see Naim’s reply. At present I use my mac to communicate with the Core and there’s no problem. However, when I open file explorer on my windows 11 pc, though I can see the core in network, I can’t open it getting a message whch says it is unsecure. I’m using Windows 11 Home and apparently it doesn’t recognise the gpedit.msc. This feature seems to only be accessible if you have Windows 11 Pro. There do seem to be ways of installing when I search, but I’m not confident in my computer knowledge to follow them safely.

All part of a strategy to drive the customer base into a closed, subscription based, App Store model.

Yes it’s safer for non technical customers, but really it’ll be about profit - as it always is.

BTW, Apple are further down this path than MS, Mac’s haven’t had a system account for ages making any privileged activity tricky, again especially so for non technical users.

ATB, J

SMB Sharing has been around since the 90’s and by now has reached v3.1.1. The industry is increasingly moving to phase out SMB v1 and v2 in favor of v3 due to the increased security capabilities of SMB v3.

70% or more of the companies out there however still use SMB v1. And many NAS devices out there are also still relying on this older version … The Uniti Core is no exception.

Several Windows updates disabled SMB v1, check…

Otherwise, to reach the HDD of the Core, before been able to “Map” it, you have to access it from the Network.
You double-click the Media device, you will than get a web page with an IP address.
You copy it in your file explorer, replace EVERYTHING before 192 with double \ and press return.
you will have access to the two main folders: Music and Download and it’s only those that you can “Map”.

1 Like

The UnitiCore doesn’t use SMB1. It is happy with any version of SMB2 or 3.

Yes that used to work, but it doesn’t with Windows 11 and update 2024/H2 if the PC is connected by WiFi, which is the point of this thread.

1 Like

Strange…
I just made the test… disconnect the wire, connect via WiFi…
And I can access my Core, BUT I have “only” Windows 11 23H2.
24H2 is an Insider version ?

From the relevant Microsoft page:

Windows 11, version 24H2, also known as the Windows 11 2024 Update, is now available. This latest version of Windows is being rolled out in phases, and it has now entered a new stage of availability. Version 24H2 is being offered to a wider range of eligible devices running Windows 11, versions 22H2 and 23H2.10 Dec 2024

@davidhendon @Wditters @duf666 @Chris-G @IainO

I emailed Naim support about this issue & thought that you all may like to see their reply:-

Thank you for your email.

Our software team keeps up to date with changes that could affect the operations of the Core, and other devices, and will no doubt update things so that functionality can continue. What that update will look like, is up to the software department, but I can’t foresee the Core’s functionality being reduced if there’s something that we can do about it.

I’ll send the thread to the software team to see what they say,

I will let you know if there is any follow up.

3 Likes

This solved the issue for me:

Microsoft SMB Guest fix

2 Likes

FYI…
I too now updated to 24h2, and still have access to my Core…

1 Like