I have a win32 (TASBS) program that will only run on a win 32 system.  To run it on Windows 10 I have to set up a hyper V machine with WinXP.  It wasn't a pleasant experience but here is what I did.

I got a valid WinXPPro iso and Key

Created a new machine in HyperV and loaded the iso in the media disk and installed the operating system.

It will work for about 30 days but if you need it for longer you have to activate it, but microsoft doesn't support xp anymore.  Even so you can still activate it by phone.  

1.  Click the activate button and select activate by phone.

2.  A phone number will appear (some other local ones may work).  Call the number and say you are activating windows.  One of the next prompts is to use the auto-activation method (don't use any of the others).  You will then be asked to read the activation code on the screen and they will give you code to enter into the machine. (takes about 10 minutes).  If you can mange to enter about 50 characters without a mistake, then it should be activated.

3. To get network connection you need to setup a switch that is connected to the physical network adapter.  

1. In the HyperV actions select Virtual Switch Manager
2. Click on New Virtual Switch
3. Select External
4. Select the network adapter you want to link to
5. Click allow management operating system to share this adapter
6. Apply.

In my case step 3 got an error. (My hyperV was installed a while ago and not used).  To resolve the error:

1. Uninstalled hyper V from Windows Features.
2. restarted the machine
3. opened an admin command prompt or PS and type: netcfg -d  (from https://techgenix.com/resolving-problems-creating-a-hyper-v-virtual-switch/ )
4. restart computer again and reinstall hyperV
5. Create a new machine and attach the disk created in 1.  
6. Create the new Virtual Switch as above.

Under the machine select settings.

1. Delete the default Network adapter.
2. Add New Hardware and select legacy network adapter.
3. For Virtual switch select the switch you just created.

I also had DNS problems as the adapter used IP6 settings.  You may need to manually change the DNS IP in the network properties of the VM's network adapter.

I had another problem with the TASFTP software that wouldn't keep my ftp settings.  I had to go into the TASFTP directory and change a file called wakeup and reenter the settings as the software was unable to save the settings.