Yes, Microsoft did it again, this time it was with KB5065426. I only lost about 3 hours figuring it out, removing the KB to allow the Win2025 server to access the Win98 SMB share. Another bit of time added in the bottomless pit of wasted time fixing SMB on Windows !

Since I'm pretty sure the KB will reinstall itself eventually, or Microsoft will invent a new way to break SMB soon. I'm searching for a more robust way to allow a bridge for retro computers running win98 and a server 2025. I'm thinking about it and I'm open to suggestion but I think ideally the following specification should be featured on the bridge :

- the bridge should be a virtual machine running on server2025 hyper-v.
- the file deposit (with all demos, music, games, sources, apps, whatnot) should be on the server2025 but the VM bridge should present it as it's own in a kind of virtual directory hosted somewhere else.
- the win98 computer should be able to get/put files on that VM bridge deposit (the virtual directory described on the point above).
- ideally, since I have only 4 retro computer, I could prepare virtual directory on the VM bridge that point to the Win98 computer so the Server2025 could access the share of a retro computer without intermediate transport. Of course, if the Win98 computer is closed, the virtual share should just fail, no need for fancy offline stuff. I dont want to make complex rsync, I'll just update my files manually when needs be.

So do you have suggestion of OS to use, software to set that up ? Suggestion I should consider for my project ? Thanks for reading my topic 😀