I'm getting the same repeated stream of
TransitStateMachineFromOffiline messages when trying to run Hearthstone on a restricted user account. This has been tested on Windows 7(x64) and Windows 10(x64)).
A similar setup has recently been suggested for Diablo3's botting/tools:
http://turbohud.freeforu...ead/2980/protect-warden
https://www.ros-bot.com/...ess-user-account-355763
Heathranger is started with admin privileges (Rightclick -> Run as Administrator), but if your current user has no admin rights, it's started on an admin user account. I guess this is why HearthRanger fails on TransitStateMachineFromOffiline.
If you want to reproduce this test, create a new windows account that doesn't belong to the administrators-group.
This user needs full permissions on the folders
C:\ProgramData\Blizzard Entertainment and
C:\ProgramData\Battle.net to be able to start Hearthstone.
Then either:
- Login as the new created user.
- Start Battle.net / HS as usual
- Run HearthRanger as Administrator.
or:
- Still logged in as user with admin rights.
- Hold down shift + open context menu on Battle.net --> Run as other user --> select the new created account
- Run HearthRanger as Administrator.