Presist UMCI Unlock for rs1 devices via official package - Windows 10 Mobile Apps. and Games

Install the package in attachment using IUTool and have fun. It modifies the same registry key, but it is persist as it is installed as a update package. Furthermore it is **Microsoft Windows Production signed** so it can be recognized as official package on Windows 10 Mobile, even though it is packed for Windows 10 IoT Core.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS. I tried to install something interesting (e.g. Microsoft-OneCore-IoTUAP-NanoRDP-Package.cab), but the lack of some servicing component(e.g. driver installation) makes it impossible to realize. Staging will be successfully carried out, however errors will occur during update application. I retrieved DULog later, it reported that no component could handle inf installation. And for Microsoft-IoT-PowerShell-Package.cab package, a file collision error reported as some files in the package already exist in Windows 10 Mobile image.
But in general, all packages, signed by Microsoft Windows, should pass security validation on Windows 10 Mobile, regardless the applicability.
And for Windows 10 Mobile Enterprise, I think ApplyNoMicrosoftSignedUpdapte CSP may be useful, if we can add something into Trusted Publisher certificate store (as described on TechNet) and install custom updates.

---

imbushuo said:
Install the package in attachment using IUTool and have fun. It modifies the same registry key, but it is persist as it is installed as a update package. Furthermore it is **Microsoft Windows Production signed** so it can be recognized as official package on Windows 10 Mobile, even though it is packed for Windows 10 IoT Core.
PS. I tried to install something interesting (e.g. Microsoft-OneCore-IoTUAP-NanoRDP-Package.cab), but the lack of some servicing component(e.g. driver installation) makes it impossible to realize. Staging will be successfully carried out, however errors will occur during update application. I retrieved DULog later, it reported that no component could handle inf installation. And for Microsoft-IoT-PowerShell-Package.cab package, a file collision error reported as some files in the package already exist in Windows 10 Mobile image.
But in general, all packages, signed by Microsoft Windows, should pass security validation on Windows 10 Mobile, regardless the applicability.
And for Windows 10 Mobile Enterprise, I think ApplyNoMicrosoftSignedUpdapte CSP may be useful, if we can add something into Trusted Publisher certificate store (as described on TechNet) and install custom updates.
Click to expand...
Click to collapse
what's the benefit of this?

---

Where you get packages for IoT?

---

iammomin said:
what's the benefit of this?
Click to expand...
Click to collapse
According to the cab content, it changes this registry key value:
PHP:
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CI">
<registryValue name="UMCIAuditMode" valueType="REG_DWORD" value="0x00000001" />
</registryKey>
allowing execution of unsigned code (actually, MS docs said the value should be 0x02 for unsigned code but I believe 0x01 do the same). But I'm unsure about this hack usability on W10M platform.
And this signed (by Microsoft) package can be installed on any W10M phone; you don't need to be interop-unlocked.

---

sensboston said:
According to the cab content, it changes this registry key value:
PHP:
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CI">
<registryValue name="UMCIAuditMode" valueType="REG_DWORD" value="0x00000001" />
</registryKey>
allowing execution of unsigned code (actually, MS docs said the value should be 0x02 for unsigned code but I believe 0x01 do the same). But I'm unsure about this hack usability on W10M platform.
And this signed (by Microsoft) package can be installed on any W10M phone; you don't need to be interop-unlocked.
Click to expand...
Click to collapse
have u tested 0x01 code on W10M?
is it works?