DISM does not work in Windows Thin PC...

Discussion in 'Windows Embedded' started by dersonpg, Feb 11, 2016.

  1. dersonpg

    dersonpg MDL Junior Member

    Feb 6, 2012
    54
    4
    0
    Personally, I could never remove any package installed Windows ThinPC using the commandline tool (DISM.exe) . Everytime I try to remove some package the tool returns the following error: 0x800f0825. the command I use is (example): dism /online /Remove-Package /PackageName:WinEmb-MediaPlayer~31bf3856ad364e35~x86~~6.1.7601.17514. Someone could tell me what might be causing this error? :g:
     
  2. kaljukass

    kaljukass MDL Addicted

    Nov 26, 2012
    931
    315
    30
    What Windows version you want to install it? Windows 7?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. 100

    100 MDL Expert

    May 17, 2011
    1,346
    1,544
    60
    #3 100, Feb 11, 2016
    Last edited by a moderator: Apr 20, 2017
  4. dersonpg

    dersonpg MDL Junior Member

    Feb 6, 2012
    54
    4
    0
    I checked the log file. Interestingly, there is a passage that says " DISM Provider Store: . PID = 3468 Failed to get and initialize the PE Provider Continuing by assuming That It is not the WinPE image . " .. Windows Thin PC is nothing more than WES7 . What I can not understand is that if you add packages and want to remove them later using the DISM it works normally but if you remove the packages that are already built into ThinPC then it does not work !!

     
  5. 100

    100 MDL Expert

    May 17, 2011
    1,346
    1,544
    60
    I don't think dism.log is going to be of much help because the actual package management stuff is done in CBS. DISM is only relaying any errors that CBS reports.

    I don't have a TPC/WES7 install handy, but you could try looking into the values in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\<package>\Owners, for preinstalled packages and for ones you have added yourself. My guess is that any packages you install will have themselves listed as owners, while the preinstalled ones may not. If that's the case, try adding another DWORD entry with the same name as the package in its "Owners" key also (using the same numerical value as for the packages you have installed yourself) and see if you're able to remove the package then.
     
  6. dersonpg

    dersonpg MDL Junior Member

    Feb 6, 2012
    54
    4
    0
    Your tip worked! thank you 100:worthy::worthy::worthy: