MSRA no longer works in Start 10

MSRA no longer works in Start 10

from Stardock Forums

Windows 10 MSRA used to work with Start 10.  However, now when MSRA is launched it throws the following error message:

msra.ese - Bad Image

c:\Program Files (x86)\Stardock\Start10\Start10_64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.  Error status 0xc0000428.

Also, pop up error message cannot be closed.  To get rid of it I have to reboot the computer.

Windows 10 Version 1909 (OS Build 18363.476)
Start 10 Version 1.8

start10
4,503 views 4 replies
Reply #1 from Stardock Forums Top

 Hello,

Would you Please do this PURGE: https://forums.stardock.com/486022/start10-support-faq#reinstalling

Reboot and ReInstall the latest version from your account https://store.stardock.com/myaccount/products/

Reboot test and report back here please .

 

AzDude
Stardock Community Assistant

Reply #2 from Stardock Forums Top

This is a known bug in the later versions of Windows 10.  Basically Microsoft messed up and it impacts a number of applications.  It seems they have little desire to fix it in a timely manner though.

There is a workaround however.  Follow the instructions here : 

https://forums.stardock.com/496396/get;3757154

Ashes of the Singularity II
Reply #3 from Stardock Forums Top

Quoting AzDude, reply 1

 Hello,

Would you Please do this PURGE: https://forums.stardock.com/486022/start10-support-faq#reinstalling

Reboot and ReInstall the latest version from your account https://store.stardock.com/myaccount/products/

Reboot test and report back here please .

 

AzDude
Stardock Community Assistant
End of AzDude's quote

 

Well...that didn't work!

Reply #4 from Stardock Forums Top

Quoting Neil, reply 2

This is a known bug in the later versions of Windows 10.  Basically Microsoft messed up and it impacts a number of applications.  It seems they have little desire to fix it in a timely manner though.

There is a workaround however.  Follow the instructions here : 

https://forums.stardock.com/496396/get;3757154
End of Neil's quote

This worked!  Thanks!