OC not starting with windows anymore

[whmxtra]

After updating to the latest version today I've noticed OC is not starting with windows anymore. I have unchecked/rechecked the box to make it start with windows, verified it's on the startup list in both task manager and windows settings and yet it still isn't starting.

Is there a new setting somewhere I've missed or is it a bug? Or is it just me, although only thing I've changed in the last couple days was updating OC itself. Any ideas?

It's not a gigantic issue for me since I have a fast ssd drive it runs from so only takes about 2 seconds to load from a cold start anyways but just wondering what's up with that.

[OneCommander Support]

Try unchecking and checking this again, then right-click OC in taskbar, view log, to see if there is an error settings that registry key.

Check also in Task Manager, Startup tab, and look for OneCommander entry there that it is enabled.

Clicking that option OC creates OneCommander key under

Computer\HKEY_CURRENT_USER\Microsoft\Windows\CurrentVersion\Run

so you can check it there too

[whmxtra]

03:14:23 INF] Panels reloaded

[03:14:23 INF] MSG: File opened

[03:14:24 INF] Window deactivated:Personal

Just stuff like that, no errors, already did the task manager/startup stuff, it's enabled, I even disabled, rebooted, re-enabled and rebooted again to see if that would kick it into gear. No luck.

You sure about that reg entry? There is no run folder under that directory, there is an Explorer folder, under that is "startup approved" folder the a run folder 

Computer\HKEY_CURRENT_USER\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run

Under that area there is an entry for OneCommander which looks to be fine.

But that's it. I am on the dev insider version of windows and I know they made some changes to regedit in this version but nothing that should affect this, my last update was earlier in the week, like tuesday, and the problem didn't start till Friday.

Now under

Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run (which I think is what you meant to type lol) 

there is a startup entry for OC:

"C:\Apps\OneCommander\OneCommander.exe" -nowindow

I've tried modifying and even deleting the key and then enabling autostart again via OC and checking the entry, it just won't start no matter what I do lol. FYI I am an experienced windows expert and a programming/coder myself so feel free to give me more advanced instructions for testing etc, will also keep testing on my own.

It's just weird that it was fine one day and not the next lol. Especially when it only happened after updating OC itself.

Technically I could just drop a shortcut in the shell:startup folder and force it but then it'd probably open up the window rather than going straight to the task overflow.

[whmxtra]

ROFL, you're gonna love this. I completely and totally forgot that I had set OC to run as admin (can't remember why) but apparently something in the latest version causes it not to autostart when it's run as admin. So I changed it to not run as admin anymore, logged out and back in and it autostarted just fine.

[OneCommander Support]

Thanks for the update on this. I never ran anything on start as admin so I wouldn't know the process for that, but I anyway recommend running it as standard user. There are posts around this forum about the reasons

[whmxtra]

Right click program, click run as admin box, click apply, done. It's that simple actually. But for security reasons it's not actually a good idea, I only did it because I was testing something last year, then got distracted and totally forgot that I'd set it till I had this issue lol. Just the way my setup works, I don't use the taskbar, start menu etc etc. (that stuff is all hidden). I use a dock program with docks on the bottom and side with most of my programs there (easily hidden when not needed), then I have drawers that slide out from the side of my screen which have my files etc in them. So I don't use any kind of file manager all that often so it's easy to forget when I modify something, usually it's no big deal but this time it came back to bite me lol.

[OneCommander Support]

Yes, I mean without the UAC prompt. But just to copy from other thread the reasons not to run as admin:

...this would make it run in Admin context, which might mean showing different context menu items, different mounted drives or network folders, different file associations when opening files, files or folders created though it might have Admin as owner instead of current user and some programs might have issues accessing those files, it will have different Environment variables, registry associations will be for admin user, other programs will not be able interact with it through drag&drop, or utilities like Powertoys might not be able to dock it... there might be other quirks due to permissions that I am not aware of, and all is do the the way Windows works