M
MarkRobinson7
MarkThis is an issue Ive had since the October update and is still not resolved despite a lot of effort from Support.
Basically, as the header says, some 32 bit programs I use as part of my work, which used to work fine under W10 64, ceased to do so after the update. Instead of starting properly they appear as background processes, chewing up CPU and memory but in no way accessible. Other 32 bit programs I use were completely unaffected and still work fine.
Has anyone else had this same issue and come across a fix?
The first effort to resolve this with Microsoft Support resulted in losing valuable data and consequently a work contract that I had all but completed. We've rolled back to the last build and delayed the update but it kicked in a few days ago while i slept.
The compatibility troubleshooter has not been any help at all.
Any insight would be very welcome.
Many thanks
Mark
Continue reading...
Basically, as the header says, some 32 bit programs I use as part of my work, which used to work fine under W10 64, ceased to do so after the update. Instead of starting properly they appear as background processes, chewing up CPU and memory but in no way accessible. Other 32 bit programs I use were completely unaffected and still work fine.
Has anyone else had this same issue and come across a fix?
The first effort to resolve this with Microsoft Support resulted in losing valuable data and consequently a work contract that I had all but completed. We've rolled back to the last build and delayed the update but it kicked in a few days ago while i slept.
The compatibility troubleshooter has not been any help at all.
Any insight would be very welcome.
Many thanks
Mark
Continue reading...