none
SCCM 1902 - Deployment Uninstalls Failing RRS feed

  • Question

  • We are currently trying to set up software deployments via Software Centre to client machines.  The install of the application works well, however the uninstall is providing an error 8007010b.

    Please see details below:

    LOG:

    +++ Starting Uninstall enforcement for App DT "Visual Studio Code" ApplicationDeliveryType - ScopeId_A2F1D63E-249A-49CB-911A-2E76D7C8E3E4/DeploymentType_facddd10-ea6e-4a70-8753-5b1bdc675be2, Revision - 17, ContentPath - C:\Windows\ccmcache\r, Execution Context - System    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
        Performing detection of app deployment type Visual Studio Code(ScopeId_A2F1D63E-249A-49CB-911A-2E76D7C8E3E4/DeploymentType_facddd10-ea6e-4a70-8753-5b1bdc675be2, revision 17) for system.    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
    +++ Discovered application [AppDT Id: ScopeId_A2F1D63E-249A-49CB-911A-2E76D7C8E3E4/DeploymentType_facddd10-ea6e-4a70-8753-5b1bdc675be2, Revision: 17]    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
        App enforcement environment:
        Context: Machine
        Command line: unins000.exe /silent
        Allow user interaction: No
        UI mode: 1
        User token: null
        Session Id: 2
        Content path: C:\Windows\ccmcache\r
        Working directory: "%programfiles%\Microsoft VS Code"    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
        Prepared working directory: "C:\Program Files\Microsoft VS Code"    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
        Prepared command line: "C:\Program Files\Microsoft VS Code\unins000.exe" /silent    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
        Executing Command line: "C:\Program Files\Microsoft VS Code\unins000.exe" /silent with user context    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
        Working directory "C:\Program Files\Microsoft VS Code"    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
    ScriptHandler::EnforceApp failed (0x8007010b).    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
    AppProvider::EnforceApp - Failed to invoke EnforceApp on Application handler(0x8007010b).    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
    CommenceEnforcement failed with error 0x8007010b.    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
    Method CommenceEnforcement failed with error code 8007010B    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)
    ++++++ Failed to enforce app. Error 0x8007010b. ++++++    AppEnforce    30/09/2019 17:34:25    2420 (0x0974)

    Local Directory:

    All file are present and correct in the local directory of the client machine.  All filepaths within the log itself are valid and work.

    Deployment Type Details:

    run: unins000.exe /silent

    in: "%programfiles%\Microsoft VS Code"

    I can see this bit works from the log file, and that the resulting path is valid.

    Detection Methods (all paths use the %program files% variable for the exes)

    check code.exe exists in the install dir ("%programfiles\Microsoft VS Code")

    check unins000.exe exists in the install dir ("%programfiles\Microsoft VS Code")

    Again, I know these work as the install itself works without errors and the detection method detects the application successfully.

    Is there anyone who could offer me a little assistance - as I am about to throw my PC out of the window!!!!


    • Edited by M Rains Tuesday, October 1, 2019 8:16 AM typo
    Tuesday, October 1, 2019 8:10 AM

Answers

  • Hi,

    for VSCode you dont need any source to remove it, just use this as your command line for uninstall in the deployment type uninstall section.

    "%programfiles%\Microsoft VS Code\Unins000.exe" /verysilent

    Verysilent will not display the uninstall progress bar :)

    Once that is set clients will need to update policy to see the change which by default is 1 hour or you can run a machine policy update on the collection \ client.

    If you still get issues visit the client device with the issue.

    Open a command prompt past the above without the /verysilent and see what happens.


    Richard Knight | Collection Refresh Manager | Automate detection rules for patch \ msp files | Twitter


    • Edited by Richard.Knight Tuesday, October 1, 2019 12:03 PM
    • Marked as answer by M Rains Tuesday, October 1, 2019 1:39 PM
    Tuesday, October 1, 2019 11:54 AM

All replies

  • hi 

    did you check the directory ?

    the Error 8007010B ==> "Directory name is invalid"

    did you check the  C:\Windows\ccmcache\r ?? 

    i guess you can also use this 

    https://gallery.technet.microsoft.com/SCCM-List-of-State-Message-864851d0

    | Please Mark This As Answer if it solved your issue | 
    | Please Vote This As Helpful if it helps to solve your issue |
    | Disclaimer: 
    This posting is provided with no warranties and confers no rights. |
    | N 48° 8' 39.8419" E 11° 36' 1.3359" |


    Klaus



    Tuesday, October 1, 2019 8:44 AM
  • Klauss,

    Thankyou for that - I had indeed not checked the ccmcache/r folder.

    The uninstaller is not actually located in here.  I presumed it would use the one local to the machine already in the program file folder.

    Do I need to add the uninstaller itself into the software share on the SCCM server for the client to pull down as opposed to using the local one???  Surely not.

    Tuesday, October 1, 2019 9:59 AM
  • hi 

    well i guess you need to check the uninstall string

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[YOUR PRODUCT]

    and check this value "UninstallString" this will point you to the uninstall location

    is the Caller is MSI, the Folder is also the same (local MSI Cache)

    | Please Mark This As Answer if it solved your issue | 
    | Please Vote This As Helpful if it helps to solve your issue |
    | Disclaimer: 
    This posting is provided with no warranties and confers no rights. |
    | N 48° 8' 39.8419" E 11° 36' 1.3359" |


    Klaus

    Tuesday, October 1, 2019 11:45 AM
  • Hi,

    for VSCode you dont need any source to remove it, just use this as your command line for uninstall in the deployment type uninstall section.

    "%programfiles%\Microsoft VS Code\Unins000.exe" /verysilent

    Verysilent will not display the uninstall progress bar :)

    Once that is set clients will need to update policy to see the change which by default is 1 hour or you can run a machine policy update on the collection \ client.

    If you still get issues visit the client device with the issue.

    Open a command prompt past the above without the /verysilent and see what happens.


    Richard Knight | Collection Refresh Manager | Automate detection rules for patch \ msp files | Twitter


    • Edited by Richard.Knight Tuesday, October 1, 2019 12:03 PM
    • Marked as answer by M Rains Tuesday, October 1, 2019 1:39 PM
    Tuesday, October 1, 2019 11:54 AM
  • There are two versions of VSCode, one is 32-bit and one is 64-bit. Which are you trying to uninstall? This is important as 32-bit version gets installed into c:\program Files (x86) so you need to check the box on the application for whether the app is 64-bit or not.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, October 1, 2019 1:01 PM
  • Hi,

    for VSCode you dont need any source to remove it, just use this as your command line for uninstall in the deployment type uninstall section.

    "%programfiles%\Microsoft VS Code\Unins000.exe" /verysilent

    Verysilent will not display the uninstall progress bar :)

    Once that is set clients will need to update policy to see the change which by default is 1 hour or you can run a machine policy update on the collection \ client.

    If you still get issues visit the client device with the issue.

    Open a command prompt past the above without the /verysilent and see what happens.



    This worked.  Thankyou for the help.

    FYI it is the 64 bit i am trying to push out.  Next step is to push out teh regedits for the context menu :D

    Thanks

    Mark

    Tuesday, October 1, 2019 1:40 PM