BDP3 file transfer from windows 11 PC

geordienp

BDP3 file transfer from windows 11 PC
« on: 24 Feb 2026, 01:45 am »
I own a BDP-3 and have just bought a new PC running Windows 11 (Home). I am unable to get my PC to see the BDP3's file structure and cannot drag and drop music files between my PC and USBs and SSD attached to the Bryston over my home network. This wasn't a problem with my old Windows 10 PC. I think the problem arises from Windows refusing to communicate with SAMBA, specifically SMB1. Is there a fix for this? I have spent the last couple of days ploughing through my PC's Windows settings with Co-pilot AI to no avail. The conclusion was:
"Windows 11 Home (22H2 and later) cannot connect to SMB1 devices that require anonymous guest access. Microsoft removed this capability at the OS level. Your Bryston uses:
•    SMB1
•    Guest access
•    No credentials
Windows 11 now blocks that combination permanently."


geordienp

Re: BDP3 file transfer from windows 11 PC
« Reply #2 on: 24 Feb 2026, 11:32 pm »
Yes, this is very familiar and is presumably the scource used by the AI Co-Pilot. I tried many of these to no avail.

Blueshound

  • Jr. Member
  • Posts: 62
  • Matrix Audio Featuring the T10 Active System
Re: BDP3 file transfer from windows 11 PC
« Reply #3 on: 25 Feb 2026, 01:14 pm »
Over the past year or so, a small number of Windows 11 updates have broken the ability of the operating system to link to external devices, such as NAS or other storage drives not in the computer itself. In all of those cases, none of the suggested fixes have worked. Typically the capability was restored by the next update. The issue was well documented on Microsoft's own support forums.

You may know that you're current on updates, but if you're not sure, check status of updates. Also check File Explorer - can you not only see but select your music file storage locations, and see them open on screen? (Your opening post says no, but just confirming.) After the problem updates, this didn't work for me, and returned an error message.

I also use a BDP3 and BDA3, including a hard drive installed in the BDP3.

May not be your issue, but something to be aware of. Now I never allow an update without having set a restore point first.

Brian

ttsto

  • Jr. Member
  • Posts: 145
Re: BDP3 file transfer from windows 11 PC
« Reply #4 on: 25 Feb 2026, 03:21 pm »
I had discovery problem on W10 though, the other way around - BDP1 vas not seeing my PC share, and I was able to solve it by enabling SMB1 despite warnings and creating user bryston in windows
Plus restarts after changing settings, many tutorials omit the need for restart before trying if it works
Now is over, with music library on NAS - transfer speed is great too

cleeds

  • Jr. Member
  • Posts: 42
Re: BDP3 file transfer from windows 11 PC
« Reply #5 on: 25 Feb 2026, 08:29 pm »
I also use Win11 with a BDP3 and BDA3. If engaging SMB 1.0/CFIS File Sharing Support in Windows and then rebooting does not resolve the issue, you might try entering the BDP's IP address into your browser. (Ideally, the best approach is to assign the BDP a fixed IP address from within your router. That will prevent a lot if issues in Windows.)

Rush2112

  • Jr. Member
  • Posts: 21
Re: BDP3 file transfer from windows 11 PC
« Reply #6 on: 26 Feb 2026, 10:26 pm »
In search bar type in windows features . Go to Smb1.0 and check all boxes . If the windows 11 pc does not see the hard drive unplug and restart the bdp3 .

soopergoo

  • Jr. Member
  • Posts: 15
Re: BDP3 file transfer from windows 11 PC
« Reply #7 on: 5 Mar 2026, 01:00 am »
I had this exact problem with W11.  Its was an issue after 24H2 was released.  I hope this helps. 

Follow these steps to turn off the SMB Signing feature via Group Policy on Windows 11 Pro, Enterprise, or Education:
1.   Open Start on Windows 11.
2.   Search for gpedit and right-click on the top result to access the Group Policy Editor.
3.   Navigate to the following path:
Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
4.   Right-click the “Microsoft network client: Digitally sign communication (if server agrees)” policy and select Properties.
5.   Select the Disabled option.
6.   Make sure “Microsoft network client: Digitally sign communication (always)” is also Disabled if Not Defined.
 
7.   Click the Apply button.
8.   Click the OK button.