i want to debug an eVB app on my pocketpc2003 but eVB (platform manager) checks via RAPI the version of the target device:
cemgr.exe_2868.Log
Code:
cemgr.exe,CeRapiInit[Ex],31401933,0,0,Start,Wed Sep 12 11:26:09 2006
cemgr.exe,,31401943,10,10,Exit,,0x00000000
cemgr.exe,,31401943,10,10,CEAPI,0,0,0,0x00000000
cemgr.exe,GetSystemInfo,31401983,50,0,Enter
cemgr.exe,GetSystemInfo,31401983,50,0,Call,16
cemgr.exe,GetSystemInfo,31402123,190,140,Return,52,0x00000000
cemgr.exe,GetSystemInfo,31402123,190,140,Exit,,0x00000000
cemgr.exe,GetSystemInfo,31402123,190,140,CEAPI,1,16,52,0x00000000
cemgr.exe,CeGetVersionEx,31402123,190,0,Enter
cemgr.exe,CeGetVersionEx,31402123,190,0,Call,4
cemgr.exe,CeGetVersionEx,31402133,200,10,Return,34,0x00000000
cemgr.exe,CeGetVersionEx,31402133,200,10,Exit,,0x00000000
cemgr.exe,CeGetVersionEx,31402133,200,10,CEAPI,1,4,34,0x00000000
cemgr.exe,RPCClientUninit,31402133,200,0,Enter
if the version info does not match => an error is displayed.
=> how to prevent platform manager from verifying the os version?
Related
Hi,
I flashed touch-it rom on my trophy and later on tried to flash the htc original which half bricked my bootloader (one line only). So I'm stuck on touch-it. I installed dutch language and updated to 7740 through cab method.
Recently zune mentions theres a htc update, so I try it but it fails with error 0x80180048. Exact error:
================================================
START OF UPDATEVALIDATOR ERROR MESSAGES
================================================
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\11E534F5-CAC2-4E07-AD88-F9CD61673A14.101.pks\HTC_OEMAPPS.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.51006.401 GUID = {47C557C0-08B2-493C-A380-08C72D78E3BA}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_OEMAPPS cannot find a path to highest expected version of: 2250.21.51006.401
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x80180048
=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================
UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE: HTC_OEMAPPS.cab.pkg ERROR CODE: 0x80180008 Total number of Bad Packages: 1
Process Failed with code 0x80180048
Is there anybody that can help me please? Or is there no other option but to send to repair centre? Thanks for your trouble
I installed Windows 10 a few days ago. Since then, my computer regularly restarts and says it's because of a BUGCODE_USB_DRIVER error. This seems to only be a problem when I have my wireless keyboard and mouse attached through a wireless USB device. I have a Microsoft sculpt comfort keyboard and mouse.
So far, I've:
Uninstalled and reinstalled all USBs.
Updated all of my drivers.
Completely reinstalled Windows 10.
Updated the computers BIOS.
I thought the last step resolved the issue as I was able to use my wireless mouse and keyboard for roughly three hours before my computer restarted itself. . Please help. This is driving me insane, and I need this computer to work, among other things. Here's my system information and a crash dump analysis
System Information (local)
computer name: MASTER-PC
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\WINDOWS
Hardware: 10249RU, LENOVO, Emerald Lake
CPU: GenuineIntel Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8499900416 total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081315-16765-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_GetHciMn+0x1096B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:48:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081315-17750-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE0001F817560, 0xFFFFE0001F37FA50, 0xFFFFE00020D1CA0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:19:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081315-17703-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001F2DA49D0, 0xFFFFE001F3C0EAE0, 0xFFFFE001F50C34DC)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:07:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081315-22093-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001A0CEEB60, 0xFFFFE001A2070470, 0xFFFFE001A201344C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 8:16:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081315-40312-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001E199DCF0, 0xFFFFE001E24BCA90, 0xFFFFE001E68E1A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Yesterday, I was running some apps (WeChat, Photo, etc) on my phone, but then my phone starts to lag, and suddenly restart by itself, and the following error appears after small NOKIA logo:
"ERROR: Unable to find a bootable option. Press any key to shutdown"
I've tried all possible solution I've found, which is:
1) Hard reset key combo: hold "volume down" until exclamation mark shown. (no exclamation mark shown for me)
2) Windows Device Recovery Tool
- it shown model phone is "Lumia phone" and Firmware version is unknown.
- When press install, it shown error once it starting to flash FFU, and show "Operation ended with failure. Software installation failed. Please try restarting your device, and try software installation again..."
3) Nokia Care Suite
- same as WDRT, when boot to flash mode, it shown error when the program try to flash FFU.
- FFU downloaded by WDRT, it shown error that said FFU is invalid
- FFU downloaded from http://lumiafirmware.com/ error message
Code:
DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
Exception:
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
4) "Unbrick Lumia without JTAG"
- THOR2 can't find connection on the following command
Code:
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
Error:
Code:
Debugging enabled for emergency
Initiating emergency download
Operation took about 11.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
- can't "flash" vpl to phone
Code:
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Nokia\Packages\Products\rm-915\XXX.vpl
Error
Code:
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_059S3J0_3058.50000.1425.0004_034.vpl
Process started Fri Sep 30 19:47:41 2016
Logging to file C:\Users\...\AppData\Local\Temp\thor2_win_20160930194741_ThreadId-4880.log
Parsing VPL file C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_059S3J0_3058.50000.1425.0004_034.vpl
Successfully parsed VPL
Flashing .ffu file RM914_3058.50000.1425.0004_RETAIL_apac_malaysia_307_04_441880_prd_signed.ffu (SW version 3058.50000.1425.0004)
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 1
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 220
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 15269888
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot disabled
Secure FFU disabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_3058.50000.1425.0004_RETAIL_apac_malaysia_307_04_441880_prd_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 15269888
CID: Samsung, Size 7456 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is disabled.
Secure eFUSE is disabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT, startsector = 15269854
UEFI returned error: 4
Clear GPT has failed!
Operation took about 9.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 196611 (0x30003)
5) Try to flash FFU with WPInternal
- Doesn't work for flashing FFU (Error shown when trying to flash, Error 0x1106: Security header validation failed)
- Somehow flashing separate partitions (EFIESP, MainOS, Data) works, but I've flash old ROM that I've backup doesn't work
- able to boot to mass storage mode, able to read, able to backup (don't know about write)
Please help me, I've tried all of these above and my phone still bricked :crying:
Did you find the solution and unbrick your phone?
It sounds like the Flash memory in your phone is going bad or at least has some bad blocks. The error states that the phone reported an error while trying to flash over the image
i connect not one, 3-4 pieces to jtag riff box. the problem is emmc/nand memory, this chip have a bug, is not the only one have this problem.
the state of the memory chip is READ ONLY!, so you can't write this.
one box apear and change the state of the memory on other phones with same kind of problem. need to send some special command to emmc to change the state.
today morning my lumia 520 just hang up and rebooted and shown me no bootable options press any key to reboot..but i cant recover it with WDRT ,WPI or any...any my observations are say its partition are converted GPT to MBR .
can anyone help me to give instruction to part it..
attachment are given below.
thanks
Hi,
you might try:
if your mobile still is in mass storage mode, try to mount ffu file with IMGMOUNT utility, then try to repartition MSM and copy single partitions. I do not know much about MSM partitioning, so please verify my advise with someone more experienced!
Alternatively:
SFFU programming and Full NVI update:
thor2 -mode uefiflash -ffufile "your ffu file name" -do_full_nvi_update -do_factory_reset
I had a case where it worked to recover from flight mode & no IMEI issue.
You have to localize thor2.exe in a command line window, preferable as administrator.
You will find thor2.exe in C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
When ffu file is not accepted, try to drop ffu file statement
Best whishes!
JoachimP said:
Hi,
you might try:
if your mobile still is in mass storage mode, try to mount ffu file with IMGMOUNT utility, then try to repartition MSM and copy single partitions. I do not know much about MSM partitioning, so please verify my advise with someone more experienced!
Alternatively:
SFFU programming and Full NVI update:
thor2 -mode uefiflash -ffufile "your ffu file name" -do_full_nvi_update -do_factory_reset
I had a case where it worked to recover from flight mode & no IMEI issue.
You have to localize thor2.exe in a command line window, preferable as administrator.
You will find thor2.exe in C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
When ffu file is not accepted, try to drop ffu file statement
Best whishes!
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile "F:\LumiaDeviceRecovery\RM-914\1.ffu" -do_full_nvi_update -do_factory_reset
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile F:\LumiaDeviceRecovery\RM-914\1.ffu -do_full_nvi_update -do_factory_reset
Process started Tue May 23 11:25:55 2017
Logging to file C:\Users\AMBALI~1\AppData\Local\Temp\thor2_win_20170523112555_ThreadId-7928.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 0
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 0
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 0
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot disabled
Secure FFU disabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file F:\LumiaDeviceRecovery\RM-914\1.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 0
CID: Unknown ManId: 0
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is disabled.
Secure eFUSE is disabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
UEFI returned error: 0xfa000006
Do backup to the RAM of device failed!
0xFA000006: Backup failed. Reason(s): FlashApp cannot find partition.
Operation took about 42.00 seconds.
THOR2_ERROR_FA_ERR_PARTITION_NOT_FOUND
THOR2 1.8.2.18 exited with error code -100663290 (0xFA000006)
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>
So if your device still goes to MSM (e.g. using WPInternals or a thor2 command) try to repartition it and copy the partitions from mounted ffu file.
Otherwise the only way is JTAG programming.
Best whishes!
JoachimP said:
So if your device still goes to MSM (e.g. using WPInternals or a thor2 command) try to repartition it and copy the partitions from mounted ffu file.
Otherwise the only way is JTAG programming.
Best whishes!
Click to expand...
Click to collapse
doesen't switch to mass storage mode
Hi,
please have a look at this thread: look for a developer ROM for your model and try. Unfortunately I sold my bricked device, so I cant. I had a look at Lumia Firmware, but found no developer ROM, so I guess, you could give these PWBASSY ROMs a try?
Regards,
Joachim
Here is error message. What is the problem?
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict
validation.
Windows cannot install package king.com.CandyCrushSaga because this package depends on another package that couldn't
be found. This package requires minimum version 14.0.25426.0 of framework Microsoft.VCLibs.140.00 published by
CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US to install; the frameworks with name
Microsoft.VCLibs.140.00 available to the user are Microsoft.VCLibs.140.00_14.0.22810.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00_14.0.22810.0_x86__8wekyb3d8bbwe. Pro
Windows cannot install package king.com.CandyCrushSaga because this package depends on another package that couldn't
be found. This package requires minimum version 14.0.25426.0 of framework Microsoft.VCLibs.140.00 published by
CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US to install; the frameworks with name
Microsoft.VCLibs.140.00 available to the user are Microsoft.VCLibs.140.00_14.0.22810.0_x64__8wekyb3d8bbwe
Microsoft.VCLibs.140.00_14.0.22810.0_x86__8wekyb3d8bbwe. Provide the correct framework along with this package.
NOTE: For additional information, look for [ActivityId] 64d436b7-a167-0000-4d85-d46467a1d401 in the Event Log or use
the command line Get-AppxLog -ActivityID 64d436b7-a167-0000-4d85-d46467a1d401
At line:1 char:1
+ Add-AppxPackage .\king.com.CandyCrushSaga_1.1310.1.0_x86__kgqvnymyfvs ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (C:\Users\Rex\De...vnymyfvs32.Appx:String) [Add-AppxPackage], IOException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand