Open-shell-menu: windows upgrade requests admin

[Muramas]

After windows gets upgraded Open Shell needs to reconfigure

When attempting to click okay it requests admin access. Is there a way to not need admin to make this configuration? What ends up happening is that our users are prompted this every reboot after a windows update.

[Ibuprophen]

Did you try reinstalling the Open Shell software over the current one to see if it helped?

I'm just thinking that one or more of the Windows Upgrade processes may have reverted/affected the Open Shell software somewhere.

~Ibuprophen

[Nicholas-Steel]

Since it has always required Admin access to complete the reconfiguration, the Op's post is more of a feature request for devs to research.

[paraworlds2]

Speaking of this, it would solve some headaches if there was a registry file or stand-alone "reconfiguration" file that can be run silently that we could run remotely or put in group policy or configuration manager so that our non-admin users don't have to call us up every time they get a big update from Microsoft? I'd like to automate this somehow.

[semajnitram]

That is an excellent suggestion, we have many remote workers and when this
issue hits the help desk it's a real headache.

On Tue, 22 Jan 2019, 21:20 paraworlds2 <[email protected] wrote:

Speaking of this, it would solve some headaches if there was a registry
file or stand-alone "reconfiguration" file that can be run silently that we
could run remotely or put in group policy or configuration manager so that
our non-admin users don't have to call us up every time they get a big
update from Microsoft? I'd like to automate this somehow.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Open-Shell/Open-Shell-Menu/issues/131#issuecomment-456567618,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AslK9kAfUZ52AiGeCub6hhRufkChtUtNks5vF4CMgaJpZM4Z-Yul
.

[Muramas]

That is an excellent suggestion, we have many remote workers and when this issue hits the help desk it's a real headache.
…
One issue that happens for us is that multiple users just ignore it every day and it becomes an escalated issue where there is a negative view of the program due to seeing the prompt every day.

[Nicholas-Steel]

Never understood those people Muramas. If it didn't stop appearing the last 3 times... why keep thinking it'll disappear without hitting OK!???

[thewizard1002]

There is a registry key and a value that has to match the version of windows you are running on. When windows upgrades this value is no longer correct so you get the notice. I use a batch file to fix this when I upgrade our machines. It runs whenever we install or upgrade Windows. I'll test this on the current version and leave another post with the file if it still works.

[semajnitram]

That sounds excellent and would be very grateful if you shared your file!

On Thu, 7 Feb 2019, 20:58 thewizard1002 <[email protected] wrote:

There is a registry key and a value that has to match the version of
windows you are running on. When windows upgrades this value is no longer
correct so you get the notice. I use a batch file to fix this when I
upgrade our machines. It runs whenever we install or upgrade Windows. I'll
test this on the current version and leave another post with the file if it
still works.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Open-Shell/Open-Shell-Menu/issues/131#issuecomment-461593198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AslK9tLSryxjDBpKPr_BpAsR6PqFpZybks5vLJN-gaJpZM4Z-Yul
.

[thewizard1002]

Here is the script I made for Classic Shell to fix this issue. I have rewritten it for Open Shell and tested it by upgrading from 1803 to 1809. Run it however you want. If you use SCCM you can run this after Windows has upgraded in your Task Sequence or as a separate Task Sequence that runs after an
autofix_os.zip

upgrade. If you are on a domain, you can just push out the registry key with the correct value and ONLY apply the GPO to the correct version of Windows 10. Each version will have a different value. This must be ran as an admin or as system.

[ge0rdi]

@thewizard1002
Since Open-Shell 4.4.138 it is possible to run:

%ProgramFiles%\Open-Shell\StartMenu.exe -upgrade -silent

That will perform all necessary tasks without any user interaction.
So, you can run this command from SCCM upgrade task.

[ge0rdi]

I have created wiki page regarding this issue:
https://github.com/Open-Shell/Open-Shell-Menu/wiki/OS-upgrade-without-user-interaction

[NebelNidas]

@ge0rdi Wouldn't it be better to always perform a silent upgrade by default? Everyone using Open Shell wants this action to be performed anyways, so I don't think there's a point in asking every time.

[ge0rdi]

@NebelNidas
I'd rather avoid creation of scheduled task that does something with full admin right silently.

There is usually no problem to acknowledge one message box (and provide UAC credentials) after OS upgrade (which happens quite rarely).

Administrators can setup the silent task if they are OK with it and know what they are doing.

[NebelNidas]

Hmm, ok. 🤔 I can understand your security concerns, but in my opinion the benefits outweigh the risks. I as a power user can easily discard the message, but for the many (tech-illiterate) friends and relatives I've installed Open Shell for, it makes them think they have a virus or something (also, some don't have admin rights...). If you really can't be pursuaded, could this at least be made into an option in the installer? Like a "Always perform a silent update after Windows upgrade" checkbox?

[ge0rdi]

Personally, I don't intend to work on this (as I don't like the idea at all).
Maybe someone else will take care of it.