I assumed that the Installer was a little confused about things, as it was also using the 'new Saved Games location' talked about above, but it didn't know where D2 was actually installed to. This was understandable, since I was running it from an old installation folder - one that Windows 10 didn't automatically 'know about', since installing 10 as a Dual-Boot with Windows 8.1 - I hadn't gone through the Diablo2 Installation Process with Windows 10, at this point. I looked around the BattleNet forii, but nothing was being said - at least about problems with the Installer doing this - so I did some Troubleshooting of my own and found that Diablo2 wasn't listed in the Programs and Features section ('Uninstall or Change a Program') of the Windows Control Panel. Īt the time, these buttons did not work at all.

The above location assumes that C: is your main Windows drive/partition (where Windows is installed to, which is created and used automatically, by Default) and it should also be noted that your User Name or Login Name goes where it says ''. The above location is now where your '.D2S' and '.MAP' files are kept (your Character's save game information) - and where we'll be going to get Ladder-Only Runewords working in Single Player mode in a bit. Here though, I want to get into the changes that I noticed with these Patches, how the game worked in Windows 10 for me personally, and how Windows seems to handle the game files themselves now.įor example, the Save Games for Diablo2 are no longer kept within the Installation Directory (the folder where the game is installed to) - as of Patch 1.14 they are now located at: Although I did not personally have any issues with these Updates, some people have, as can be seen if you browse the Support Forum for Diablo II (under 'Classic Games' at BattleNet). For those of you interested in playing (or never stopped playing) Diablo 2, you may have noticed there was both a Ladder Reset (on May 17th) and some new Patches (up to 1.14 now).

Diablo 2 save game 1.14