1

I'm fairly new to the world of Powershell and currently I'm trying to push a Powershell script via Intune to the company devices (all Windows 10 21H2 machines) that will show the file extensions in File Explorer.

So far, I've found this:

Set-Itemproperty -path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced' -Name 'HideFileExt' -value 0

The PS script is pushed via Intune to a test device and the monitor tells me the policy is applied successfuly but the file extensions are still not visible.

Is there something wrong with the line of code?

Razjan Baram
  • 11
  • 2
  • 2
    The script works fine. I am positive that it is not applied successfully, despite Intune telling you it did. While it is not part of that question, I suppose you should check the user context in which the script is applied and if the eventvwr or any other possible source tells you why the script did not apply correctly. Also, after trying the script locally for myself, you need to refresh the explorer tab via f5 for the change to apply. – Bowshock Feb 09 '22 at 14:10
  • 1
    I checked and indeed, the problem was Intune and not the script. Intune used the credentials of the user logged in to run the script (and thus not an elevated Powershell prompt). After changing it from user context to device context, it worked Thankyou for your answer! – Razjan Baram Feb 09 '22 at 15:16

2 Answers2

1

My original comment which helped:

The script works fine. I am positive that it is not applied successfully, despite Intune telling you it did. While it is not part of that question, I suppose you should check the user context in which the script is applied and if the eventvwr or any other possible source tells you why the script did not apply correctly. Also, after trying the script locally for myself, you need to refresh the explorer tab via f5 for the change to apply.

Solution was to set it as system/device rights, since it was indeed run as user context, hence solving the problem.

Bowshock
  • 190
  • 5
0

This was the solution:

"The script works fine. I am positive that it is not applied successfully, despite Intune telling you it did. While it is not part of that question, I suppose you should check the user context in which the script is applied and if the eventvwr or any other possible source tells you why the script did not apply correctly. Also, after trying the script locally for myself, you need to refresh the explorer tab via f5 for the change to apply" – Bowshock

Razjan Baram
  • 11
  • 2