Issues with one of the latest Betas, at least with 15.1.1.17

[ranko]

After logging in into Windows 10 Pro I am always getting prompted for Administrator Password,
because a net command wants to be executed.

I didn't change my Process Lasso Pro config so I think this is because of the Beta versions which I tried because of my wish to get a global toggle for performance mode.

Took some time to find this out.
Restored a lot of backups.
Also the backup from 6.10.24 had this issue with version v15.0.1.16.

After deinstallation of Process Lasso Pro the issues are gone.

Do you have any idea what might be causing this?

[ranko]

Same issue with latest release version 15.0.1.16.

I start the core engin as a service at system boot and
I enabled that all processes become managed that PL has access to.

These settings I am using since years successfully.

[Jeremy Collake]

That can occur in limited user accounts when the Governor service (core engine) is not started at the time Process Lasso is launched. As a last-ditch effort, it is trying to use the 'net' command to start the service, hence the request for elevation.

Check the "Process Lasso Core" service config in the Windows Services console. Make sure it is set to "Automatic".

As you discovered, I don't think it is related to any recent changes to Process Lasso.

[ranko]

Hi Jeremy, many thanks for your friendly and prompt reply.

I wondered why this happened of all sudden, as I am working without admin bit for my user since decades and this with process lasso pro since 2019, meanwhile 6 years.

I solved the issue by reinstalling 15.1.1.17 Beta and this time I choosed to reset the config.

Regarding config reset .. Nevertheless, 2 clicks further during installation
I selected again my two folders for config and logs under my users Documents.
So PLP started again with the same config like I always use.

This time I did not become prompted with the net user command.
I tried 3 reboots and fresh logins, no issues anymore. I think the "reset configuration" option during setup (sorry I can't recall the exact name anymore) solved the issue. Yesterday I didn't use this option.
I am only wondering what is being reset, as yesterday and today I choosed my "custom config folder"
K:\<username>\Eigene Dokumente\0-Bitsum Process Lasso\config

[ranko]

Of all sudden it started again...
Maybe related with upgrade to 15.0.2.18?

[ranko]

After restoring my disk image of 2d ago, where everything worked with the beta,
I have again this issue with the net command on login.

I am quite often restoring my system entirely by a Macrium Reflect disk image.
Since years I did not have issues like this.

I am wondering what has changed, I had never such issues before.
Sorry, but I will have to deinstall PLP if this can't be fixed, because it really nerves.

[ranko]

The startup mode of the Core Engine is set to automatic in the services.

Jeremy, I'm sorry, but I don't understand. I haven't had any problems like this for years.

Now all of a sudden Process Lasso Pro has startup problems and asks for admin rights again with the net command.

The funny thing is that a few days ago it worked again for a few days. Today I had to restore the Macrium disc image from yesterday and the whole thing started again.

I have also done the restore with Macrium what feels like 100 times in the past few years. I always do it to uninstall the programme thoroughly if I don't like something.

I've been struggling with these problems again for about 2 hours now and it's getting really annoying.

Neither uninstalling nor reinstalling the latest stable or beta fixes the problem.

It makes no difference whether
- I use my own folder K:\<loginname>\My Documents\0-Bitsum-Process-Lasso\
  with the subfolders config and logs, which has been working perfectly for years
- or to reset everything and use the folder C:\ProgramData\ProcessLasso\config

This is really frustrating and I'm fed up with it for now, I don't want to see this annoying prompt again the next days when I log in, so I'm uninstalling PLP.

It's a pity but I'm so fed up with it now, I want to slowly get some peace and quiet back into my setup and not waste time every few days up to a few hours with such things.

[Jeremy Collake]

I'm so sorry that I missed your replies to this thread! I suppose they got buried with spam.

We have tentatively resolved this as of v15.0.4.3 BETA:

(3) GUI: Address a startup race condition that could result in net.exe being used as a fallback attempt to start the Governor service, causing a console window to briefly show, or a request for elevation in the case of limited users.

The particular timing of the GUI startup in relation to the service startup was important, hence the variation about when you saw it.