Windows 10: Can we make Microsoft store in an organization request admin credentials when installing an...

We need to be able to make the users still access the store but not be able to download any apps without the admin credentials, this would be preferable in intune but can really be in anything as long as we can send it out remotely.

:)

 

Minecraft installation in Microsoft store

Hi,

Thank you for writing to Microsoft Community Forums.

We understand your concern as you are unable to install Minecraft in Microsoft Store. In order to get clarity and to assist you accordingly, please reply with the answers to the questions below:

• What is the Windows 10 version and Build installed? (Type
  winver in Windows search/Run command)
  

• Do you have any non-Microsoft antivirus program installed?
  
• Does this issue occur for all games & apps from the store?
  

• What is the date and time on the PC and ensure it is correct?
• Do you get any error message or code?

Meanwhile, we would suggest you to perform these steps and after every step check if you are able to install the game.

Step 1: Reset the Windows Store Cache: Press the Windows Logo Key + R to open the
Run dialog box, type wsreset.exe, and then select OK.

Note:
A blank Command Prompt window will open, and after about ten seconds the window will close and Microsoft Store will open automatically.

Step 2: Run the Windows Store Apps Troubleshooter: Select the
Start button, and then select Settings>Update & Security
> Troubleshoot, and then from the list select Windows Store apps > Run the troubleshooter.

Step 3: If you have any non-Microsoft security/antivirus software installed, disable it temporarily and then try installing the game.

Step 4: If the issue persists, then we would suggest you to create a new administrator user account and check, refer this article to

create a local user or administrator account in Windows 10.

Regards,

Aditya Roy

Microsoft Community – Moderator

 

Re-Installing the Microsoft Store

Hi Wisedred,



Thank you for writing to Microsoft Community Forums.



In this scenario we would suggest you to perform these steps to Reinstall and Re-Register all Windows apps for all accounts.

1. Press Windows + X key and select Windows PowerShell (Admin).
   
2. Copy and paste this command, then press enter:
   Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
   
3. Close the PowerShell command and restart the PC.
   
4. Open Microsoft Store and install the game.

If the issue persists, then we would suggest you to create a new administrator user account and check if you are able to open Microsoft Store and then install the game, refer this article to
create a local user or administrator account in Windows 10.



Regards,



Aditya Roy

Microsoft Community – Moderator

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.