Skip to content

Instantly share code, notes, and snippets.

@helloyanis
Last active October 7, 2025 23:24
Show Gist options
  • Save helloyanis/6d9b1e7fc82ed9ce2507e0d7f71ff333 to your computer and use it in GitHub Desktop.
Save helloyanis/6d9b1e7fc82ed9ce2507e0d7f71ff333 to your computer and use it in GitHub Desktop.
[FIX] How to use MicroSD management on New Nintendo 3DS with Windows 10 and above

This tutorial will make you bypass the following problem when connecting to your New Nintendo 3DS from a Windows PC

Network Error

Windows cannot connect to [3DS name here]

Check the spelling of the name. Otherwise, the might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

Error code: 0x80070035

The network path was not found.

The reason for the problem is that the 3DS uses an old unsecure network protocol called SMB1 that has been disabled by Windows. But don't worry, we can enable it again!

Step 1, open Terminal

Go in Windows search, search for "Terminal" and it should appear! Open it, you will see a black window

image

Step 2, install the old protocol that the Nintendo 3DS uses.

Copy the command below, then right-click in the terminal to paste it, and press enter. ⬇️

Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

You will have a confirmation prompt, press enter again to proceed.

You will also probably be asked to restart your computer, so press enter do it.

Step 3, activate that protocol!

After restarting, open an administrator terminal window. You need this to enable the protocol.

image

The tab name should say "Administrator", and you get the same black window as before.

Now copy and paste the command below in the terminal, just like before : ⬇️

Set-SmbServerConfiguration -EnableSMB1Protocol $true

Press enter to confirm and you should be able to connect to your 3DS!

Step 4, Connect to your 3DS!

It should work normally now! Go to your file explorer's network tab, find your Nintendo, 3DS, and connect! Move your files, do whatever you want!

Step 5, disable the protocol

After doing that, you can disable the protocol by pasting this in your administrator terminal!

Set-SmbServerConfiguration -EnableSMB1Protocol $false

Press enter, then enter again to confirm. You have disabled the protocol now! Remember to do this when you're done transferring files to not leave yourself vulnerable.


And you're done! If later you want to re-connect, you can start from step 3 because the SMB1 protocol is already installed on your PC!

Did this help? Click on the "Star" button on the top right of this page to help it get referenced better by search engines!

Did this not help? Ask your questions in the comments below! I won't reply necessairely but they are public so someone else might!

Thanks for reading and have fun!

@helloyanis
Copy link
Author

Which error does it give?
Yes SMB1 should be disabled afterwards, which is what step 5 is for. It's insecure but it's how your 3ds communicates to the PC so there's no way around at, even your method should use SMB1 under the hood, I think.
I tried it again and it still works fine

@ciaopirlo-cmyk
Copy link

Always Error code: 0x80070035

@helloyanis
Copy link
Author

Did you get anything after enabling the SM1 protocol in the command prompt?

Try running

Get-SmbServerConfiguration | Select EnableSMB1Protocol

and you should see True. If you see False then the protocol is disabled and that won't work
screenshot

@ciaopirlo-cmyk
Copy link

ciaopirlo-cmyk commented Sep 17, 2025

Cannot try now, i don't need SM1. FTPD doesn't use SM1 , and is better.

@helloyanis
Copy link
Author

Cannot try now, i don't need SM1. FTPD doesn't use SM1 , and is better.

Well, I for sure can't argue with the "Mine is better" argument ( ̄~ ̄;)

I'm not sure how it can communicate with the 3ds without smbv1 since that's the 3ds protocol but good if it works for you

@Gigamatts
Copy link

Tried this and it didn't work. I also did the Get test and got True. In the end I got the same 0x80070035 I would get with or without SMB1.

@thhpii
Copy link

thhpii commented Sep 21, 2025

I didn't have this problem about two months ago, but I ran into this error today. This did the trick for me. Thanks!

@dpsd18139
Copy link

i also followed every step here and the other method where you check the checkbox via the "turn windows features on or off" and nothing worked for me either

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment