- Local time
- 12:55 AM
- Posts
- 11
- OS
- Windows 11 Pro
Okay, we haven't been able to identify a fix for my problem, but I do offer some final observations for those who may find themselves in the same situation.
x86 applications:
All of my older applications did either (1) transfer correctly, or (2) ran correctly in Windows 8 compatibility mode following transfer. Some did then require reactivation, and I was able to provide all of those codes from saved emails - some of them from many, many years ago.
64-bit applications:
(1) Many of my 64-bit applications did transfer correctly (some requiring reactivation). All of those applications did NOT have a space in the C:/Program Files execution path. (2) The other 64-bit applications, those with a space in their filepath, did run correctly (some requiring reactivation) after I copied the contents of their application folders to new folders without spaces in their filepath and created shortcuts invoking the new paths.
I would prefer that there had been no problems. I hope that some of you are right and that the issue of spaces in the filepath is the result of using the transfer program, but given my overall findings of general success I don't think that any of us can say for certain that that was the actual issue here. I am left, of course, with the need to download test versions before purchasing any new software to insure that it doesn't also have the "Windows cannot find ... " problem.
I have been involved in computing since writing my first COBOL program in 1962(?) and recognize that sometimes the best we can do is to find a workaround. Anyway, thanks to all of you for your interest and your suggestions.
x86 applications:
All of my older applications did either (1) transfer correctly, or (2) ran correctly in Windows 8 compatibility mode following transfer. Some did then require reactivation, and I was able to provide all of those codes from saved emails - some of them from many, many years ago.
64-bit applications:
(1) Many of my 64-bit applications did transfer correctly (some requiring reactivation). All of those applications did NOT have a space in the C:/Program Files execution path. (2) The other 64-bit applications, those with a space in their filepath, did run correctly (some requiring reactivation) after I copied the contents of their application folders to new folders without spaces in their filepath and created shortcuts invoking the new paths.
I would prefer that there had been no problems. I hope that some of you are right and that the issue of spaces in the filepath is the result of using the transfer program, but given my overall findings of general success I don't think that any of us can say for certain that that was the actual issue here. I am left, of course, with the need to download test versions before purchasing any new software to insure that it doesn't also have the "Windows cannot find ... " problem.
I have been involved in computing since writing my first COBOL program in 1962(?) and recognize that sometimes the best we can do is to find a workaround. Anyway, thanks to all of you for your interest and your suggestions.
My Computer
System One
-
- OS
- Windows 11 Pro
- Computer type
- PC/Desktop
- Manufacturer/Model
- HP
- CPU
- 12th Gen Intel(R) Core(TM) i7-12700K 3.60 GHz
- Memory
- 64.0 GB (63.7 GB usable) RAM
- Hard Drives
- 4 TB NVMe SSD




