waykagent still displaying on user login even though told not too

Hello Simon,

Could you tell us what version of the Wayk Agent you are deploying? 2021.1 was released last week and it contains a lot of fixes and improvements, including for the options not saving correctly: https://wayk.devolutions.net/release-notes/wayk

Would it be possible to verify the following on one of the Wayk Agents that are not behaving normally? Go to %ProgramData%\Wayk and open WaykNow.cfg. It is a JSON file, and in it you should see (near the middle):

    "AutoLaunchOnUserLogon": true,
    "ShowMainWindowOnLaunch": false,

Please validate that the boolean values are correct.

Best regards,

Hi Richard,

yes i am using the latest version 2021.1.0 - Windows 10 Pro
and i can confirm the variables are set correctly

{
    "AccessControl": {
        "Viewing": 1,
        "Interact": 1,
        "Clipboard": 1,
        "FileTransfer": 1,
        "Exec": 1,
        "Chat": 1
    },
    "Language": "en",
    "AutoLaunchOnUserLogon": true,
    "ShowMainWindowOnLaunch": false,
    "MinimizeToNotificationArea": true,
    "VersionCheck": false,
    "DenEnabled": true,
    "DenUrl": "wss://remote.xxxxx.com",
    "QualityMode": 1,
    "LoggingLevel": 1,
    "AutoUpdateEnabled": true,
    "PersonalPasswordType": 0,
    "AllowPersonalPassword": true,
    "AllowSystemAuth": true,
    "AllowNoPassword": true,
    "GeneratedPasswordLength": 6,
    "GeneratedPasswordCharSet": 1,
    "ChatLogEnabled": true,
    "AnalyticsEnabled": true,
    "CrashReporterAutoUpload": true,
    "SchemaVersion": 1
}

NowService Debug log from %programdata%\Wayk - https://pastebin.com/raw/2JLcaQfc
WaykAgent Debug log from %appdata%\Wayk - https://pastebin.com/raw/LkXNiF4t

logs from a second reboot and it happening
NowService Debug Logs https://pastebin.com/raw/TjQNhqNP
WaykAgent debug logs https://pastebin.com/raw/vK3TbDq8

logs from a third reboot with TRACE set instead of debug
NowService Trace Logs https://pastebin.com/raw/P12p2MKS
WaykAgent Trace Logs https://pastebin.com/raw/L3JH7Nkt


Regards

Simon

Hi Simon

I remember this issue and I'm sorry you're still having a problem, even intermittently.

For the affected user, can you check for the presence of this registry value:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\WaykNow

or in the local machine hive, e.g.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WaykNow

And if it's present - delete it.

Older versions of the application registered for auto launch by registering at that point in the registry. Ultimately we moved away from the approach, as managing per-user registry values from a "global" application just proved too annoying. The installer might have failed to clean that up on a prior upgrade.

Let us know what you find

Thanks and kind regards,

Hi Richard,

nothing exists at those two entries in the registry, so its not that issue, it must be something else

Regards

Simon

Hey Simon

Thanks for checking.

On the affected system, can you download and run Autoruns? It's a portable executable. You can run it, and save the output then send it to us via PM or at wayk@devolutions.net.

Thanks and kind regards

Hi Richard,

im a developer myself and ive already checked the autoruns application, and nothing sticks out apart from nowsession.exe being listed as expected

but sure will send output over for you

Regards

Simon

Hi Simon

Thanks for the assistance debugging this.

This looks like a bug on our side; I've entered a ticket for that and a fix will be available in the next release. I'll update this thread at that time.

Thanks again, and sorry for the inconvenience

Hi Richard,
I'm glad you found the bug!
any chance of explaining the bug?
I'm always interested in how things work!
DM me if you want :)
Regards
Simon

Hey Simon

The unnecessary activation happens because WaykAgent.exe is already running when the service tries to "auto launch" it (or vice-version: the service "auto launches" the agent, and then something else tries to launch it as well).

Internally, the service has a few code paths that lead to launching the Agent; generally to work around Windows weirdness with things like fast boot, hibernation and Windows 10 ability to relaunch running applications after a reboot (older versions of Windows called this "Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart" but it's changed recently).

There is a code path that skips a check if WaykAgent.exe is already running before launching it (specifically to prevent inadvertent activation). I can't tell you exactly how you're hitting that only sometimes. We could probably determine it by logging the boot process with ProcMon, but that's tricky (it needs to be explicitly enabled on *every* boot) and it will likely just lead us to the same solution anyway!

Kind regards,

Hi Simon

Just letting you know that Wayk Agent 2021.1.1 is now available. Please let us know if you still have the problem after updating.

Thanks and kind regards,

Hi Richard,

laptop VM updated to 2021.1.1 automatically,

1. shutdown the VM after it updated to 2021.1.1
2. started the VM up,
3. it auto logged in with my user (no password)
4. lone behold, the application was open on screen

sadly the issue is still there! its still opening up even tho its told not too!

any advise?

EDIT: i have DM you log files

Regards

Simon

Hi Simon

I'm sorry to hear that; not immediately sure what the problem is but thanks for sending the diagnostics. We will look into this next week and write back here with an update.

Thanks and kind regards,

Hi Simon

I'm thoroughly confused by this issue.

The updated logs you sent show that the service is only attempting to launch the Agent once; however the log is also a bit confusing in terms of the sequence of events. I assume it's related to fast boot or another state restoration done by Windows at startup.

Can you enable process auditing on the machine? Start > Run "gpedit.msc" to open the policy editor. Then navigate to "Computer Configuration > Windows Settings > Security Settings > Local Policies > Audit Policy" and find the policy "Audit process tracking". Open it up and check both boxes.

Windows will write an entry in the Security event log for process creations and deletions. If we can see the corresponding event log the next time this happens, it may give some insight.

Thanks and kind regards,

Hi Richard

when I get chance I will try for you and send you logs

however, since the update, every time I start up the vm, the windows open on screen to begin with,

where as before the update it would only happen every so often, maybe after a few reboots but now it’s every time!

So whatever has happened has made it worse from my view

regards

Simon