BUG: Power Off via Macro at Noamd 2.8.3 Build 11

Does the shell launch, but not the software?  OR no shell?  

Do you have a startup macro assigned also?

The shell starts.
And if try then start the software it close instant.
Nope, have no startup Macro.

I not know if it is the same on a console.
Not have test it.
On the PC i have Win10.

Ah,...forgotten.
Dosen`t matter if i try start Client, Offline, Offline with VZ.
(Have at this machine no Dongle connect)

One step more done...

What i have change yesterday was my screens-monitors.
But the EOS Nomand not runs during change.
Normal, PC down, unplug the old monitor, connect the new, start win10, start EOS Nomad, FAULT...

Now i have uninstall/repair the EOS PC Software and it seems it works normal.

Nope.
The second PC not runs.
Uninstall the EOS, new install and after program a short show i get back in my neverending circle...

The Setup via Shell i can open normal.
But all other otptions not.
This PC have an Dongle.

Can you please share your show file?

Foyer 2019-06-21 16-56-07.rar

There doesn't appear to be a macro with that text in the provided show file.

Oh yes.
After i though it was the Macro i try program it new.
Without the Macro.
But thats not fixed the problem.

If i repair EOS Nomand Software -via Systemcontrol-uninstall-repai option- runs the second PC normal.
Then i transfer the show from my office PC to the second PC.
At this point i get the problem.
I have also try it with older Software 2.7.4.

So my next step will be, create this show direct on the second PC and try then a newstart.

Let us know how it goes.  Loading your show file here has given my no issues on a PC.

I have no idea.
Have now install Win10 new.
But nothing change.

If i have a patch -nothing more- in the show all is good.
I can close and open Nomad normal.

If i have store presets and/or macros in the same show i get the fault.

So, now i have install Win10 complet new.
And i hope the issue is gone.
Ah, i work with a Faytech Touchscreen Monitor.
He works with a resolution 1400x900.
Think it is a "strange" format.
it is possible this is the reason?
With newinstall of Win10 i have now change also the Monitor to a "normal" 1920x1080.
Next i will program also new and try it...

New install of win10 is done.
Copy the show from Office PC to Dimmercity PC (this the PC make me stress) is done
With Dimmercity PC i use now the normal 1920x1080 Non-Touch Monitor.
Safe show on this PC, Newstart, all works.
Now at Dimmercity runs 2.8.2 Build 8

Tomorrow i will try what happen if i conect the Faytech Touchmonitor again.
So i think, it is possible i get a driver problem at win10.
Ane the newinstall fixed it now.

Tada,... i find it out...

If i close Nomad via EXIT a few seconds later the Shell popup for restart Nomad.
But....if this PopUp come you must wait 20-30 seconds before you can start Nomad new.
Shell-Setup works instant.

So it is a "Time Out" for restart