Windows 7/32 - Desktop suddenly on the Screen but Watchout still Running in Background

[rzuern]

Using Watchout 4.3 on Windows 7 32bit, installed and tested also considered the "Windows 7 - Tweaking list".

Used and worked fine for about 24h. Suddenly - the Client Show was just started about 8 min before,

both Display Computer hided Watchout and the Windows Desktop was fully on the Screen.

But no Failure Message because Watchout was still Running AND playing all the files in the hidden Background.

After tapping (using ALT + TAB) Watchout came back in Fullscreen, and for the next 3-4 hours nothing happened again.

When the show was finished, we recognized that when pushing the "WINDOWS" button on the Keyboard the Desktop Screen came back again.

So no lock for using Watchout in Full-Screen was there.

What could have Happened ?

[PierreLucB]

This is also happening to at least 1 computer in our system at work on Windows 7 64bits and Watchout 4.3. It is very strange and not reassuring.

 

Does anyone have a thought why this is happening?

[jfk]

Using Watchout 4.3 on Windows 7 32bit, installed and tested also considered the "Windows 7 - Tweaking list".

Used and worked fine for about 24h. Suddenly - the Client Show was just started about 8 min before,

both Display Computer hided Watchout and the Windows Desktop was fully on the Screen.

But no Failure Message because Watchout was still Running AND playing all the files in the hidden Background.

After tapping (using ALT + TAB) Watchout came back in Fullscreen, and for the next 3-4 hours nothing happened again.

When the show was finished, we recognized that when pushing the "WINDOWS" button on the Keyboard the Desktop Screen came back again.

So no lock for using Watchout in Full-Screen was there.

What could have Happened ?

 

We have observed this behavior when

starting watchpoint from the Startup items at power up.

Mostly with v4, not sure if this applies to v5.1.

 

watchpoint is in distress once the events you describe occur.

the logo screen appears for a bit, then watchpoint "disappears",

the watchpoint icon may not appear on the task bar,

but as you note, it is still running hidden.

Yes, you may be able to re-invoke full screen operation, via

online or update from production, load command from IP control, or Alt-Tab,

but watchpoint is still not running correctly.

The appearance of the cursor or task bar over watchpoint in full screen is a sign of this issue.

Once you get full screen mode to re-appear, I advise you quit and restart watchpoint,

and all will be fine.

 

The watchpoint distress appears to occur from other items loading on startup after watchpoint.

You may be able to eliminate it by removing items from startup in msconfg

(Start - All Programs - Accessories - Command prompt and then type msconfig IIRC).

You can remove the Codemeter item from Startup and the keys will still work fine.

Look for other culprits in that list.