Question about Win 10 TroubleShooting-Package removal.

Discussion in 'Windows 10' started by tnx, Sep 8, 2015.

  1. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,622
    233
    60
    Hi all.

    yet another thread on package\s removal.

    I am after testing removing the Telemetry packages

    I got this bit of info off the forums, sorry can not remember what thread I found it or whom wrote it.

    Telemetry:
    Microsoft-OneCore-AllowTelemetry-Reduced-Default-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384
    Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10240.16384

    Telemetry x64:
    Microsoft-OneCore-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384
    Microsoft-OneCore-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384


    I have just now sort of started a fresh and made myself a new package list.
    Windows 10 x64 Pro image used.

    Searching my list for
    I found all these packages

    Package Identity : Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-OneCore-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-OneCore-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-base-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-base-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-net-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-net-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-WOW64-base-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-WOW64-base-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-WOW64-net-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-WOW64-net-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~en-GB~10.0.10240.16384
    Package Identity : Microsoft-Windows-TroubleShooting-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384

    My question is,

    Do all the packages need to be removed ?
    Is it safe to remove all those packages ?
    Is it best just to stick with the 4 packages from the top list, and why ?

    :cool:
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    7,711
    24,974
    240
    No
    No
    Yes, because they are the truly telemetry client, other are the old regular troubleshooting component (in CP)
     
  3. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,622
    233
    60
    Cheers for that info.

    This is the thing which sort of confuses me.

    There is as we all know a huge long list of packages. Is there a definitive list somewhere of exactly which packages can be safely removed.

    Or is there a way to look at the various package names and be able to tell what's what .

    I am removing the packages manually via DISM.