Many thanks. I think we're nearing the root cause: default user settings.
(I used to be a programmer and still enjoy investigating issues like these.
Previously I packaged Adobe Reader for our organisation (although using the old GPO and not Intune), which took quite a while but taught me a lot about default settings (which a user may later modify) and system settings they cannot.)
The popup I want to get rid of is (translated from Dutch):""Everything" needs admin rights to index NTFS volumes [...]", with 3 radio buttons. I select "Don't index NTFS volumes".
With Intune, you can install an app in System context (it's a toggle: System or User). If I omit Everything's "-app-data" and used the following command (definitely short enough), the user's ini file's still created in %appdata% the first time a user launches the app, although the popup is not shown (which I cannot explain; maybe the app still launches as admin?):Probably also because Intune runs the installer with System rights, you end up with only these two system settings in the app folder's ini file:Afterwards each user can launch the app, which creates the (very long) ini file in their own Roaming folder. That one does not contain these two system settings.
Now, the main question: where can I specify default user settings? If I want "hide_empty_search_results=1" as default (but a user can later change/overrule this), I would expect adding that line to the app folder's ini file uses it as a starting point for a brand new user's ini file:It does not. In the new (very long) user's ini file, that setting's still set to zero.
You wrote: "-choose-volumes sets the following values [...] These values are stored in your "user" Everything.ini aka %APPDATA%\Everything\Everything.ini".
My theory: just like my attempt fails to set "hide_empty_search_results=1" for *all users*, "choose-volumes" does nothing *during installation* because there is no %appdata% at that time. In contrast, running "Everything.exe -choose-volumes" *after* installation does work because only the latter modifies the user's roaming ini file.
IMO, parameters like "-choose-volumes" and "-install-config" should add settings to the shared ini file in Program Files (maybe add a "default" section for clarity?), to be used each time a new user ini file is created (in %appdata%).
Update: just found [Computer\HKEY_LOCAL_MACHINE\SOFTWARE\voidtools\Everything] - THIS is where the installation options are stored, as default starting points for the user's ini file. Is there a reason why the two-line-system-ini in the app folder exists? Would it help to choose either registry or that ini file?
In summary:
-Running "Everything.exe -choose-volumes" *after* installation works fine. In addition to the four lines we already talked about, these seven also get cleared correctly when C-drive/NTFS is disabled:-However: if you run the app (UI/frontend) when no user ini file exists, the app seems to ignore the InstallChooseVolumes=0 registry setting.
-I want to prevent that initial NTFS-popup, so that the user starts with a blank slate (not even C-drive)
-I'd also like a way to set other default user settings, e.g. "hide_empty_search_results=1"
(I used to be a programmer and still enjoy investigating issues like these.
Previously I packaged Adobe Reader for our organisation (although using the old GPO and not Intune), which took quite a while but taught me a lot about default settings (which a user may later modify) and system settings they cannot.)
The popup I want to get rid of is (translated from Dutch):""Everything" needs admin rights to index NTFS volumes [...]", with 3 radio buttons. I select "Don't index NTFS volumes".
With Intune, you can install an app in System context (it's a toggle: System or User). If I omit Everything's "-app-data" and used the following command (definitely short enough), the user's ini file's still created in %appdata% the first time a user launches the app, although the popup is not shown (which I cannot explain; maybe the app still launches as admin?):
Code:
Everything-1.4.1.1026.x64.Lite-Setup.exe /S -install-options "-choose-volumes" /D=C:\Program Files\EverythingCode:
; Please make sure Everything is not running before modifying this file.[Everything]; settings stored in %APPDATA%\Everything\Everything.iniapp_data=1run_as_admin=0Now, the main question: where can I specify default user settings? If I want "hide_empty_search_results=1" as default (but a user can later change/overrule this), I would expect adding that line to the app folder's ini file uses it as a starting point for a brand new user's ini file:
Code:
; Please make sure Everything is not running before modifying this file.[Everything]; settings stored in %APPDATA%\Everything\Everything.iniapp_data=1run_as_admin=0hide_empty_search_results=1You wrote: "-choose-volumes sets the following values [...] These values are stored in your "user" Everything.ini aka %APPDATA%\Everything\Everything.ini".
My theory: just like my attempt fails to set "hide_empty_search_results=1" for *all users*, "choose-volumes" does nothing *during installation* because there is no %appdata% at that time. In contrast, running "Everything.exe -choose-volumes" *after* installation does work because only the latter modifies the user's roaming ini file.
IMO, parameters like "-choose-volumes" and "-install-config" should add settings to the shared ini file in Program Files (maybe add a "default" section for clarity?), to be used each time a new user ini file is created (in %appdata%).
Update: just found [Computer\HKEY_LOCAL_MACHINE\SOFTWARE\voidtools\Everything] - THIS is where the installation options are stored, as default starting points for the user's ini file. Is there a reason why the two-line-system-ini in the app folder exists? Would it help to choose either registry or that ini file?
In summary:
-Running "Everything.exe -choose-volumes" *after* installation works fine. In addition to the four lines we already talked about, these seven also get cleared correctly when C-drive/NTFS is disabled:
Code:
ntfs_volume_guids="\\\\?\\Volume{1a2b1b08-5970-4888-8682-d82996f9769e}"ntfs_volume_paths="C:"ntfs_volume_roots=""ntfs_volume_includes=1ntfs_volume_load_recent_changes=0ntfs_volume_include_onlys=""ntfs_volume_monitors=1ntfs_volume_guids=ntfs_volume_paths=ntfs_volume_roots=ntfs_volume_includes=ntfs_volume_load_recent_changes=ntfs_volume_include_onlys=ntfs_volume_monitors=-I want to prevent that initial NTFS-popup, so that the user starts with a blank slate (not even C-drive)
-I'd also like a way to set other default user settings, e.g. "hide_empty_search_results=1"
Statistics: Posted by JanVP — Tue Aug 13, 2024 10:03 am