M
Mike42TW
Hello everyone,
I'm using Windows 10 Pro 64Bit.
The program in question is a flash based educational software from 2013 that is using a licensing system (All-In-One Protector | Mirage Computer Systems) to launch the actual software. The flash files are in an encrypted container file, which is supposed to be loaded with the flash player through the protector software. But I just use the program, so I can't comment on any specifics on how it works.
There were no issues using the program from Windows 7 all the way up to Windows 10 1909.
With the 2004 update, the software doesn't start correctly anymore. The licensing portion starts, and works, but it doesn't load the actual flash player.
In 1909 an earlier I can make out two tasks:
-"Protector (32 bit)" (started by the desktop shortcut)
-Microsoft(C) Register Server (32 bit) (with "Adobe Flash Player 10", started after the license has been checked
In 2004 I only get the first entry. I can still load the license manager via shortcut, but it's not working 100% as I can't activate features like setting a path for log-files, which would come in really handy.
I've tested this on several different machines (all have up to date drivers and Windows updates):
-Win 10 1909 PC with a Ryzen 3600, which I'm not updating to 2004 right now.
-Win 10 1909 Thinkpad X230, the software stopped working after updating to 2004 and worked again when going back to 1909.
-A colleague of mine has a Win 10 1903 Laptop, where the software also works and has worked for years through different Versions of Windows 7, 8 and 10.
-For further testing I also set up two virtual machines (one in VMWare and one in VirtualBox) with fresh Win 10 2004 installs and they both have the same issue. Obviously I can't roll these back to 1909 to confirm it works there, since I can't get the 1909 ISO anymore from Microsoft.
I can Install the software, the update, start the license activation and then start the program, which checks the license successfully, but doesn't hand the reigns over to flash. Or start flash at all. I'm not sure what's going on here exactly.
I contacted the developer of the software (not the license protection) and they're at a loss as well, actually not having heard of the issue yet, which isn't surprising, given that the 2004 update is fairly new and not on all systems yet.
Now, I'm not able to figure out anything else since I don't know what to look for. Is it something with Flash that changed in 2004, is is the old license protection software from 2013 that's finally not compatible anymore with current Windows or is it something else that changed in Win 10 2004?
I'd appreciate any help that might get me on the right track of understanding what the issue is. Any tests I can do or information I can supply, I'm happy to do. Just let me know.
Edit: I just went through the registry on a system that worked and figured out how to enable the logfile for the software manually on the Win 10 2004 installation.
This is the error message I'm getting:
Access violation at address 76FB6FF3 in module 'ntdll.dll'. Write of address 00610044
Oh and I forgot to mention, but any compatibility settings have zero effect on the situation and I have run everything both as administrator and a regular user.
Thanks,
Mike
Continue reading...
I'm using Windows 10 Pro 64Bit.
The program in question is a flash based educational software from 2013 that is using a licensing system (All-In-One Protector | Mirage Computer Systems) to launch the actual software. The flash files are in an encrypted container file, which is supposed to be loaded with the flash player through the protector software. But I just use the program, so I can't comment on any specifics on how it works.
There were no issues using the program from Windows 7 all the way up to Windows 10 1909.
With the 2004 update, the software doesn't start correctly anymore. The licensing portion starts, and works, but it doesn't load the actual flash player.
In 1909 an earlier I can make out two tasks:
-"Protector (32 bit)" (started by the desktop shortcut)
-Microsoft(C) Register Server (32 bit) (with "Adobe Flash Player 10", started after the license has been checked
In 2004 I only get the first entry. I can still load the license manager via shortcut, but it's not working 100% as I can't activate features like setting a path for log-files, which would come in really handy.
I've tested this on several different machines (all have up to date drivers and Windows updates):
-Win 10 1909 PC with a Ryzen 3600, which I'm not updating to 2004 right now.
-Win 10 1909 Thinkpad X230, the software stopped working after updating to 2004 and worked again when going back to 1909.
-A colleague of mine has a Win 10 1903 Laptop, where the software also works and has worked for years through different Versions of Windows 7, 8 and 10.
-For further testing I also set up two virtual machines (one in VMWare and one in VirtualBox) with fresh Win 10 2004 installs and they both have the same issue. Obviously I can't roll these back to 1909 to confirm it works there, since I can't get the 1909 ISO anymore from Microsoft.
I can Install the software, the update, start the license activation and then start the program, which checks the license successfully, but doesn't hand the reigns over to flash. Or start flash at all. I'm not sure what's going on here exactly.
I contacted the developer of the software (not the license protection) and they're at a loss as well, actually not having heard of the issue yet, which isn't surprising, given that the 2004 update is fairly new and not on all systems yet.
Now, I'm not able to figure out anything else since I don't know what to look for. Is it something with Flash that changed in 2004, is is the old license protection software from 2013 that's finally not compatible anymore with current Windows or is it something else that changed in Win 10 2004?
I'd appreciate any help that might get me on the right track of understanding what the issue is. Any tests I can do or information I can supply, I'm happy to do. Just let me know.
Edit: I just went through the registry on a system that worked and figured out how to enable the logfile for the software manually on the Win 10 2004 installation.
This is the error message I'm getting:
Access violation at address 76FB6FF3 in module 'ntdll.dll'. Write of address 00610044
Oh and I forgot to mention, but any compatibility settings have zero effect on the situation and I have run everything both as administrator and a regular user.
Thanks,
Mike
Continue reading...