SMB File Sharing Between Win10 and Win98

Whether you operate Win98 boxes in 2018 as a hobbyist or as an IT provider (oh, how I pity you in that case), you have undoubtedly discovered at some point in Win98’s impressive tenure that sharing files across a network is by far the fastest and easiest way to get new drivers and software onto such a machine, and files such as work product, screenshots and more back off such a machine. If you happen to do any of that interfacing from a Windows 10 computer, you have likely found that your ability to talk to your Win98 box mysteriously disappeared. I did, and here’s what I did to fix it.

The scenario for me: a new Windows 98SE installation on a Toshiba Libretto 60 subnotebook is in need of some drivers and software that would be extremely inconvenient to transfer via floppy disk, and the machine has very limited I/O options that can be matched by my ThinkPad W520. My go-to solution for this type of situation is to create a share on the Windows 98 computer, connect to it from the modern computer, dump all the files I need onto the 98 box all in one go, and get to work. Sometimes I’ve done the reverse with a share on the newer machine, and generally have shares setup in both directions to provide as many options as possible. In my scenario, there is no domain in the picture, just a workgroup.

In this case, I installed the PCMCIA Ethernet card driver from the C: drive, having copied it to there from a floppy disk in “command prompt only” mode (F8 menu) – the Libretto PCMCIA floppy drive requires special drivers inside of Windows, but not in true DOS. Win98 has successfully leased an IP address, can ping the router, and can be pinged by the router. Win98 can ping Win10, and Win10 can ping Win98. Sounds great, right?

Not so! Attempting to navigate to \\Win98hostname\share from Win10 gives a strange “Windows can’t access…” message with an exception 0x80004005. Attempting to navigate to \\Win10hostname\share from Win98 gives a message that the computer does not exist on the network. Yeah, that’s cool, but you can ping each other, remember?

I couldn’t help but feel this seemed familiar, as if I’d ran into it before, but had previously fixed it (and so it should remain fixed). Since Win98 certainly hasn’t changed at all in over a decade, surely Win10, which loves to just change itself into whatever it wants to be on a day-to-day basis, is at fault.

After much hair-pulling, the truth surfaced: Windows 10, following (but not directly as part of) the Fall Creators Update (1709) de-installed support for SMBv1. MS states:


  • SMBv1 now has both client and server sub-features that can be uninstalled separately.
  • Windows 10 Enterprise and Windows 10 Education no longer contain the SMBv1 client or server by default after a clean installation.
  • Windows Server 2016 no longer contains the SMBv1 client or server by default after a clean installation.
  • Windows 10 Home and Windows 10 Professional no longer contain the SMBv1 server by default after a clean installation.
  • Windows 10 Home and Windows 10 Professional still contain the SMBv1 client by default after a clean installation. If the SMBv1 client is not used for 15 days in total (excluding the computer being turned off), it automatically uninstalls itself.
  • In-place upgrades and Insider flights of Windows 10 Home and Windows 10 Professional do not automatically remove SMB1 initially. If the SMBv1 client or server is not used for 15 days in total (excluding the time during which the computer is off), they each automatically uninstall themselves.
  • In-place upgrades and Insider flights of Windows 10 Enterprise and Windows 10 Education do not automatically remove SMB1. An administrator must decide to uninstall SMB1 in these managed environments.
  • Automatic removal of SMB1 after 15 days is a one-time operation. If an administrator re-installs SMB1, no further attempts will be made to uninstall it.
  • The SMB version 2.02, 2.1, 3.0, 3.02, and 3.1.1 features are still fully supported and included by default as part of the SMBv2 binaries.
  • Because the Computer Browser service relies on SMBv1, the service is uninstalled if the SMBv1 client or server is uninstalled. This means that Explorer Network can no longer display Windows computers through the legacy NetBIOS datagram browsing method.
  • SMBv1 can still be reinstalled in all editions of Windows 10 and Windows Server 2016.


As we see above, my ThinkPad running Windows 10 Pro, which was updated in place to 1709, apparently automatically uninstalled SMBv1 support after 15 days of not using it. Since I do not regularly work with my Win98 hardware, this is completely plausible. According to the MS wording above, we are assured that if we re-add SMBv1 support, it will ‘stick’ and not automatically undo itself again.

To re-add SMBv1 support, navigate to Control Panel (as much as MS wants you to not see it anymore), go to Programs and Features, then Turn Windows Features On or Off. You will find SMBv1 as “SMB 1.0/CIFS File Sharing Support” which has 3 sub-items: Automatic Removal (ha! don’t install this!), Client, and Server (both of which may be beneficial depending on exactly what you’re doing).

Check the boxes for the items you want (my approach is client and server), reboot when prompted, and presto – your Win10 1709 computer can now talk to your Win98 computer again.

Quick note for completeness:
If you are looking to initially set up sharing between Win98 and Win10, there’s more to it than just the above. You will also need to change the Local Security Policy setting, Network Security: LAN Manager Authentication Level  to “Send LM & NTLM responses”, and of course enable file sharing on the Win98 machine and log on using Client for Microsoft Networks.

11 thoughts on “SMB File Sharing Between Win10 and Win98

  1. Flemming Jacobsen

    Thank you very for sharing your knowledge. I had spent countless weeks, watching YT videos and reading forum posts. Everything that worked for them, never worked for me. This time it worked, and I’m best pleased. Thanks

  2. Steve Sybesma

    After more testing the policy change you recommend is not what makes this work because I reverted back and I have bidirectional access between Windows 10 1809 and Windows 98SE. The policy change seems to have no effect positive or negative.
    I overcame the issue with not being able to access Windows 10 shares from Windows 98SE by explicitly mapping a drive to the Windows 10 1809 share.
    In other words, clicking on the machine in Network Neighborhood won’t work.
    The SMB1 issue between Windows 10 1809 and DOS cannot be overcome by any amount of settings changes after all the testing I did.
    Microsoft added deprecation packages to 1809 that do not exist in earlier builds like 1703, which I tested and sharing works both directions with DOS.
    I have yet to test 1709 and 1803.
    Some helpful items that could make a positive difference with SMB1:
    1. Open Powershell and run these three commands:
    Set-SmbServerConfiguration -EnableSMB1Protocol $true
    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
    sc.exe config mrxsmb10 start= auto
    2. Go to Internet Options, Security tab and change security level of Local Intranet (your home network) to LOW and open Sites and make sure the box is checked “Include all network paths (UNCs). Since network paths are affected by the security level, it makes sense to set it to LOW.

  3. Steve Sybesma

    Noticed one thing about the Security Option setting. Once set I do not see anyway to back out of it. Hmmm…

  4. Steve Sybesma

    I have several VMs and it’s interesting to know I can access shares on my Win98SE VM from Windows 10 but not the reverse, I can access shares between my Win98SE VM and my DOS VM, and I used to be able to access shares from my DOS VM to my Windows 10 VM (that was with a later version of 10 than I have now).
    It sure would be great to force Windows 10 to play nice and loosen up a bit.

    1. Steve Sybesma

      Correction: I used to be able to access shares from my DOS VM to my Windows 10 HOST machine, not VM

  5. David Erhart

    Thanks. This worked for me for a Windows 10 64-bit system to a Windows 98SE system. The Windows 10 system can access shares on the Windows 98SE system.

  6. Mark Wilton

    Thank you for this very important document. However, I am still having problems and I am willing to bet that something changed with Windows 10 version 2004 that was installed while I was trying to configure two new Windows 10 machines.

    When I was using Windows 7, I had no problem linking shares in both directions between the Windows 7 and Windows 98se machines. I followed your instructions in configuring the Windows 10 machines. I can ping ether way. The Windows 10 machines can connect to Windows 98se shares. The Windows 98se machine knows that the Windows 10 machines exist, but cannot access the Windows 10 machines – I get a unknown or not on the network message.

    My need is for the Windows 98se machine to access the Windows 10 shares.

    Do you have any ideas as to what might cause my predicament?

    Many thanks,


  7. George Baumann

    Just wanted to say “Thank You” for posting the info on “SMB File Sharing Between Win10 and Win98” ( I opened Windows Features on my Win 10 box and turned on both of the SMB 1.0/CIFS options – Client and Server. That was all I needed to get access to the shared folders on the Win 98 box. It’s only a one-way connection, but that’s all I need.

    Thank You, and Happy New Year!


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.