IMO The explorer is crashing because the driver needs a higher version of dot.net.
Have you got a wsus server that still stores all the xp patches… this will likely solve the issues but it's surprising how many companies don't consider it worth having.
If the answer is no then that gets hard because Microsoft has turned their one off now but it largely depends on what you are trying to achieve with this:
1. For a good (supported and stable) system that will ran on older hardware… I'd Install Linux mint,
2. If it simply must be xp then your best workaround is to use a host machine running hyper-v and install the xp as a virtual machine… that way the host machines dot.net is actually what gets used to got to the internet.
IMO The explorer is crashing because the driver needs a higher version of dot.net.
Have you got a wsus server that still stores all the xp patches… this will likely solve the issues but it's surprising how many companies don't consider it worth having.
If the answer is no then that gets hard because Microsoft has turned their one off now but it largely depends on what you are trying to achieve with this:
1. For a good (supported and stable) system that will ran on older hardware… I'd Install Linux mint,
2. If it simply must be xp then your best workaround is to use a host machine running hyper-v and install the xp as a virtual machine… that way the host machines dot.net is actually what gets used to got to the internet.
So, the system need a higher .net version. I've tried finding an offline installer for .net, but to no avail. Do you have a link?