Intune: Custom Policy Configuration: Setting fails with error: -2016281112 (Remediation failed)


i am implementing Google Chome policy and using their guidance to do that:


I have created a custom policy where i have ingested the contents of Chrome.admx file.


This setting works.


However as soon as i start adding additional settings from their example policies page:

all of them fail with error: -2016281112 (Remediation failed)


Have you guys seen this error? it is getting very annoying for me.


Thanks in advance.




8 Replies



Are you trying to change the home page and add home button? if yes, I use this great ps and push with Intune Script, works like charm!


Otherwise, @Peter Klapwijk, any thoughts on why the custom config policy didn't work?




 #paths for chrome policy keys used in the scripts

$policyexists = Test-Path HKLM:\SOFTWARE\Policies\Google\Chrome

$policyexistshome = Test-Path HKLM:\SOFTWARE\Policies\Google\Chrome\RestoreOnStartupURLs

$regKeysetup = "HKLM:\SOFTWARE\Policies\Google\Chrome"

$regKeyhome = "HKLM:\SOFTWARE\Policies\Google\Chrome\RestoreOnStartupURLs"

$url = ""


#setup policy dirs in registry if needed and set pwd manager

#else sets them to the correct values if they exist

if ($policyexists -eq $false){

New-Item -path HKLM:\SOFTWARE\Policies\Google

New-Item -path HKLM:\SOFTWARE\Policies\Google\Chrome

New-ItemProperty -path $regKeysetup -Name PasswordManagerEnabled -PropertyTypeDWord -Value 0

New-ItemProperty -path $regKeysetup -Name RestoreOnStartup -PropertyType Dword -Value 4

New-ItemProperty -path $regKeysetup -Name HomepageLocation -PropertyType String -Value $url

New-ItemProperty -path $regKeysetup -Name HomepageIsNewTabPage -PropertyTypeDWord -Value 0



Else {

Set-ItemProperty -Path $regKeysetup -Name PasswordManagerEnabled -Value 0

Set-ItemProperty -Path $regKeysetup -Name RestoreOnStartup -Value 4

Set-ItemProperty -Path $regKeysetup -Name HomepageLocation -Value $url

Set-ItemProperty -Path $regKeysetup -Name HomepageIsNewTabPage -Value 0



#This entry requires a subfolder in the registry

#For more then one page create another new-item and set-item line with the name -2 and the new url

if ($policyexistshome -eq $false){

New-Item -path HKLM:\SOFTWARE\Policies\Google\Chrome\RestoreOnStartupURLs

New-ItemProperty -path $regKeyhome -Name 1 -PropertyType String -Value $url


Else {

Set-ItemProperty -Path $regKeyhome -Name 1 -Value $url

@Moe_Kinani ...Thanks for that. This script is definitely handy. However, the real question is that why would these custom CSPs not work?

I would understand that if i extract a setting from an ADMX XML and it doesn't work. maybe i am doing something wrong. But in this case, these are examples from Google. and millions of people have tried them. so why are they throwing an error.



best response confirmed by ShehzadUIT (Contributor)

Hi @ShehzadUIT 
What value are you using for HomepageLocation?

I wrote an article about managing Chrome settings and HomePage Location is one of the examples, it might be helpful for you

@Peter Klapwijk . I am using the following value for homepage:


<enabled/><data id="HomepageLocation" value="<Our_Intranet_Page_URL"/>

@ShehzadUIT you only seem to miss a space between <enabled/> and <data id

@Peter Klapwijk Thanks. that maybe one of the issues. the other issue that i saw comparing your article with the examples given by Google is:


Yours: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/HomepageLocation





when i took off the * before googlechrome and startup, the error went away.

@ShehzadUIT I missed that * in your screen shot. But glad my article helped and you solved the issue!


Any intune remediation failes ,  generates the same code. 

-2016281112 (Remediation failed)

Any Application has nothing to do with it. (It is not Application specific.) 


The challenge is how to fix it . That is pain. 

MS does not workback to solution.


We have the same challenge today, the password compliance policy change has made Windows Device Non compliant with the same error code. No solution