My Windows 10 64-bit Compatibility List

with Reinstallation Tips

* indicates that settings can be easily copied from an earlier installation; see the previous article in this series.

Firefox* – Compatible

Tip: To copy addons and bookmarks etc., copy the following folders:

Windows XP Settings: C:\Documents and Settings\username\Application Data\Mozilla\Firefox\Profiles\XXXXX.default

Windows 10 Settings: C:\Users\username\AppData\Roaming\Mozilla\Firefox\Profiles\XXXXX.default

Restart Firefox to restore bookmarks etc. and re-do any customisations.

Eudora 7.1* – Compatible

The main folder in Windows XP is C:\Program Files\Qualcomm\Eudora. In Windows 10 copy the contents to C:\Program Files (x86)\Qualcomm\Eudora then reinstall using "Custom Data Folder" specifying the same folder – this will preserve all your email.

Also copy the attachments folder (in my case, C:\Attachments) and enter the location in Eudora's setup.

While this program is getting a bit clunky these days, it still seems to be the only email client that automatically decodes incoming attachments and places them in a normal folder. This is a very useful feature in dealing with the many client files, PDF invoices etc that we receive on a daily basis.

Tip: Set up your email program at an early stage as it may contain serial numbers etc. of other programs you may have purchased in the past.

Word 97 & Excel 97 – Compatible

These 20-year-old programs seem to work just fine! From Office 97 Pro I installed Word, Excel and Powerpoint. Do a custom install and deselect Office Assistant as well as unused file filters etc.

Install Photo Editor, which is useful to extract images from Word files.

Note the Product ID (20 digit number).

The SR-2b patch fails because it tries to replace the Tahoma font, which is protected.
Go to C:\WINDOWS\FONTS and copy the Tahoma fonts to the Desktop.
Run Regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts and delete Tahoma and Tahoma Bold from there.
Run SR-2b patch which will ask for the Product ID.
The SR-2 patch doesn't end up installing Tahoma, so when finished copy the Tahoma fonts from the Desktop back to C:\WINDOWS\FONTS.

Tip: To open the more recent Word 2007 .docx files, the Microsoft Office Compatibility Pack (FileFormatConverters.exe) works OK too, with some limitations, even though it's supposedly for Office 2000 and later.

Adobe Creative Suite 2 & 3 – Compatible

See individual notes for each version below.

Given the cost of this high-end software, it's disappointing to report that Adobe software has more than its fair share of quirks, oddities and bugs. C'mon Adobe, you can do better than this!

Icons: In 64-bit Windows, icons won't show correctly. In the Windows 10 File Explorer ribbon, go to File/Open Windows PowerShell/Open Windows PowerShell as administrator. Navigate to the Program Files (x86)\Common\Adobe\Shell folder. Type the name of the .bat file, "Register64BitIcons.bat" (without quotations) and press Enter. This applies to Creative Suite 3 (below) as well. See this article on the Adobe forums.

Missing Type 1 fonts: Just to be different, Adobe Creative Suite has its OWN private fonts folder at C:\Program Files (x86)\Common Files\Adobe\Fonts. Create a shortcut to your system fonts folder in this folder, and Type 1 fonts should now show in Adobe Creative Suite.

Adobe Creative Suite 2 – Compatible

(includes Photoshop CS2, InDesign CS2, Illustrator CS2)

In 64-bit Windows, the installation program will fail. Simply replace the install directory "C:/Program File (x86)/Adobe" with "C:/Progra~2/Adobe"

Abobe Creative Suite 3 – Compatible

Autorun won't work. Instead, run SETUP.EXE from the Adobe CS3 folder on the installation media.

The Acrobat 8.0 Pro installation complains about a missing adobepdf.dll. Cancel the dialog box to continue the installation. The issue is fixed by applying the 8.1 and subsequent updates.

In a VERY annoying move, most of Adobe's updates after that are NOT cumulative, meaning you have to install them one-by-one, in order. I left mine at 8.1.3.

Adobe Reader XI – Compatible

The new Adobe Reader isn't immediately associated with PDF files (the Modern app is the default), but a popup appeared: "You have new apps that can open this type of file". Choose Adobe Reader at this point.

64-bit users don't get to see thumbnails in File Explorer, apparently a long-standing bug that Adobe still hasn't fixed. Instead, someone else has done Adobe's job for them.

PageMaker 7.01 – Compatible

Limited testing, but appears compatible. On Microsoft's website, it's shown as compatible with Windows 8, but not Windows 7!

Distiller 5.0 works, but the Adobe PS driver doesn't. Install the MS Publisher Color Printer (which is actually PostScript) on File, and the PPD shows up as expected. Print to a PostScript file and double click to distil as before.

Adobe Photoshop 5.5 – Probably compatible

Included here for a bit of a laugh, but shows what's possible. My original version of Creative Suite CS2 was a Photoshop upgrade. I had to install this ancient (1999) version as a qualifying product; it installed OK and a few minutes of testing didn't indicate any problems.

Adobe Lightroom 3.6* – Compatible

Installation media contains both 32-bit and 64-bit version, so if you're running a 64-bit OS, go for it!

If upgrading, there's lots of user data scattered all over the place. Firstly. copy the Lightroom folder including the catalog from
C:\Documents and Settings\username\My Documents\My Pictures\Lightroom (in Windows XP) to C:\Users\username\My Pictures\Lightroom (in Windows 8).

Copy presets* from (Windows XP) C:\Documents and Settings\username\Application Data\Adobe\Lightroom\Develop Presets
to (Windows 10) C:\Users\username\AppData\Roaming\Adobe\Lightroom\Develop Presets

Camera profiles*:
Win XP: C:\Documents and Settings\username\Application Data\Adobe\CameraRaw\CameraProfiles
Win 10: C:\Users\username\AppData\Roaming\Adobe\CameraRaw\CameraProfiles

Several other subfolders e.g. Export Presets may also contain user data.

Lotus Word Pro – Compatible

Autorun won't work - instead, run SETUP.EXE directly from the CD. Ignore compatibility warnings (which appear to apply to other programs in Lotus Smartsuite). Do a custom install and only select WordPro.

This installs in a separate C:\LOTUS folder which will remain from a Windows 10 upgrade. Install to the same (default) location.

No need to register - remove Lotus SmartSuite Release 9 Registration shortcut in C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.

Any old Ami Pro stylesheets can be copied from from C:\AMIPRO\STYLES to C:\lotus\smasters\wordpro.

VueScan Professional – Compatible

Copy the entire folder C:\Vuescan, reinstall the 64-bit version and re-register. Too easy, and puts most other programs to shame.

CorelDraw X3 and X5 – Compatible

I don't recall any issues during installation. I use CorelDraw X5 on a day-to-day basis and haven't experienced any problems, except that the menu bar becomes white on white! This is annoying, but the menu items become visible when you hover over them (the drop-down menus are still OK). CorelDraw X3 appears unaffected by this bug. This is fixable if you want to go to the trouble of making a custom menu - see the Corel user forums.

Irfan View – Compatible

Requires the 32-bit version of Ghostscript to view PDF files on a 64-bit system.

Google Earth 7.0* – Compatible

Windows XP settings are kept in C:\Documents and Settings\username\Application Data\Google. In Windows 10, settings are kept in an odd location, at C:\Users\username\AppData\LocalLow\Google.

Geosetter – Compatible

Before upgrading Windows XP, go to File/Backup settings. Save the resulting geosetter_settings.zip file to a 'known' folder, and use it to restore settings in Windows 10.

Metadata templates aren't restored, probably because of the different folder structure. Open geosetter_settings.zip, and manually copy items in the templates folder to C:\Users\username\AppData\Roaming\GeoSetter\templates.

Nikon Coolscan 2000 (SCSI) – Compatible (under VueScan).

The issue with these scanners is more one of getting the SCSI card to work under 64-bit Windows 10. These scanners are notoriously finicky about their SCSI card requirements, usually requiring Adaptec cards. Fortunately, patched 64-bit drivers exist for these cards; feel free to contact us for a copy.

Apparently Nikon Scan can be coerced to work in 64-bit as well, for those who prefer it. I'll insert the appropriate link here if I can locate it again.

Nikon Coolscan 5000ED – Compatible (under VueScan).

Epson Perfection 4990 Photo – Compatible

Works well with the bundled software Epson Scan as well as a TWAIN driver in Photoshop.

MYOB 15.5 – Compatible

This took a lot of trouble to get working. In my opinion it's probably the most user-unfriendly program I've come across, so that doesn't surprise me (that said, it does its job well). For instance, considering it's a 2006/07 app, I think sortable display columns have been around since about Windows 95!

In the end, the secret was to run the installer as an Administrator.

It also works fine in a Windows XP virtual machine, for example VMWare. I set up a shared folder on the Windows 10 host for the data files.

HELP FILES

Help files of older programs often use the deprecated WINHLP32.EXE file, a copy of which can be copied from your old Windows XP installation.

The existing WINHLP32.EXE in Windows 10 (just a stub which throws up an error message) first needs to be replaced. To do this, first rename it to WINHLP32-Win10.EXE or similar. This requires taking ownership of the original file; to do this, see here.

The Windows XP version of WINHLP32.EXE can then be copied to the WINDOWS folder.

You are here: Home Windows 10 My Compatibility List