Even though the built-in WindowsUpdate.admx file was present, the update policy still failed with error 2016281112 or 201628111. Let’s take a closer look at why that happens and how to fix it.
Dealing with 2016281112 (Remediation failed) for Bitlocker and ScreenLock policies. This happens very rarely on some of our devices and usually I am able to resolve it. However it's currently happening on a few devices and I have been pulling my hair our trying to figure out what the hell is causing these errors.
For the issue, here are some information you can refer to fix it. 1.Please check if there deployed BitLocker policy to these devices and whether targeted devices have enabled BitLocker on their devices.
Error 0x87d1fde8 usually appears when using Windows Intune or Azure Active Directory (Azure AD) for enrollment. This issue will prevent you from adding new accounts, so it’s crucial to fix it, and this guide will show you how to do it properly. Why does 0x87d1fde8 (2016281112) error appear?
To fix the issue, direct the users to change their password. On the Android platform, the user must accept the password change notification. On the Windows MDM desktop platform, the user must press CTRL+ALT+DEL and select Change Password, and then the new password rules will be enforced.
-2016281112 (Remediation failed) is a known issue. Please refer to Enforcing BitLocker policies by using Intune: known issues to narrow down the cause. TPM status seems to be OK, but BitLocker couldn’t be enabled. Perhaps we need to check which TPM driver is installed on the computer.
