ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Fresh Win 10 install - doesn't include crapware

    IT Discussion
    windows 10 screenconnect crapware clean install sysprep
    8
    60
    9.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch @Obsolesce
      last edited by

      @Tim_G said in Fresh Win 10 install - doesn't include crapware:

      It's odd your sysprep is failing. That hasn't happened in my experience.

      Hasn't failed yet, but did when I made my original images last year prior to AU coming out.

      1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch
        last edited by JaredBusch

        Here we go.. Time to find out.
        0_1495752279769_upload-770cd0da-cfd6-4fb0-82d6-a607a4dd7922

        I have a bunch of software to install but wanted to verify this first..

        1 Reply Last reply Reply Quote 0
        • JaredBuschJ
          JaredBusch
          last edited by JaredBusch

          Hot damn, it did work. I was acting like @Dashrender and getting over excited about shit before trying. All because the twitter icon popped in.

          0_1495752427632_upload-893f953c-203f-4a39-be4d-aecaac6d5910

          1 Reply Last reply Reply Quote 0
          • stacksofplatesS
            stacksofplates
            last edited by

            Wow reading through this makes my head hurt.

            1 Reply Last reply Reply Quote 1
            • DashrenderD
              Dashrender
              last edited by

              That Reg fix in the OP stopped working in 1607.

              Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

              JaredBuschJ 1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch @Dashrender
                last edited by

                @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                That Reg fix in the OP stopped working in 1607.

                Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

                You would be incorrect as I just clearly showed it working in 1703

                DashrenderD 1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender @JaredBusch
                  last edited by

                  @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                  @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                  That Reg fix in the OP stopped working in 1607.

                  Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

                  You would be incorrect as I just clearly showed it working in 1703

                  Maybe they added it back in 1703 due to complaints. Also, so now that you've got the image, have you deployed it and none of those crappy apps came back?

                  JaredBuschJ 2 Replies Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @Dashrender
                    last edited by

                    @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                    @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                    @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                    That Reg fix in the OP stopped working in 1607.

                    Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

                    You would be incorrect as I just clearly showed it working in 1703

                    Maybe they added it back in 1703 due to complaints. Also, so now that you've got the image, have you deployed it and none of those crappy apps came back?

                    I've never cared about them coming back.

                    1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @Dashrender
                      last edited by

                      @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                      Maybe they added it back in 1703 due to complaints.

                      I never made a 1607 - Anniversary Update image, so no idea.

                      1 Reply Last reply Reply Quote 0
                      • NerdyDadN
                        NerdyDad @Obsolesce
                        last edited by

                        @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                        @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                        @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                        I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

                        I honestly do not care if the crap is there or not.

                        But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.

                        Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
                        Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
                        

                        That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

                        If you don't remove the app using the bottom "-online" part, it'll be there for new users.

                        I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

                        Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

                        ObsolesceO 1 Reply Last reply Reply Quote 0
                        • ObsolesceO
                          Obsolesce @NerdyDad
                          last edited by

                          @NerdyDad said in Fresh Win 10 install - doesn't include crapware:

                          @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                          @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                          @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                          I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

                          I honestly do not care if the crap is there or not.

                          But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.

                          Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
                          Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
                          

                          That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

                          If you don't remove the app using the bottom "-online" part, it'll be there for new users.

                          I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

                          Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

                          I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:

                          Get-AppxPackage -AllUsers | Select Name | FT
                          

                          and

                          Get-AppxProvisionedPackage -Online | Select DisplayName | FT
                          
                          black3dynamiteB 1 Reply Last reply Reply Quote 1
                          • black3dynamiteB
                            black3dynamite @Obsolesce
                            last edited by

                            @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                            @NerdyDad said in Fresh Win 10 install - doesn't include crapware:

                            @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                            @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                            @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                            I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

                            I honestly do not care if the crap is there or not.

                            But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.

                            Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
                            Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
                            

                            That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

                            If you don't remove the app using the bottom "-online" part, it'll be there for new users.

                            I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

                            Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

                            I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:

                            Get-AppxPackage -AllUsers | Select Name | FT
                            

                            and

                            Get-AppxProvisionedPackage -Online | Select DisplayName | FT
                            

                            Any harm removing all AppxPackages and AppxProvisionedPackages?

                            ObsolesceO 1 Reply Last reply Reply Quote 0
                            • ObsolesceO
                              Obsolesce @black3dynamite
                              last edited by

                              @black3dynamite said in Fresh Win 10 install - doesn't include crapware:

                              @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                              @NerdyDad said in Fresh Win 10 install - doesn't include crapware:

                              @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                              @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                              @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                              I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

                              I honestly do not care if the crap is there or not.

                              But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.

                              Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
                              Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
                              

                              That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

                              If you don't remove the app using the bottom "-online" part, it'll be there for new users.

                              I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

                              Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

                              I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:

                              Get-AppxPackage -AllUsers | Select Name | FT
                              

                              and

                              Get-AppxProvisionedPackage -Online | Select DisplayName | FT
                              

                              Any harm removing all AppxPackages and AppxProvisionedPackages?

                              Yes don't do it.

                              JaredBuschJ 1 Reply Last reply Reply Quote 0
                              • JaredBuschJ
                                JaredBusch @Obsolesce
                                last edited by

                                @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                                @black3dynamite said in Fresh Win 10 install - doesn't include crapware:

                                @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                                @NerdyDad said in Fresh Win 10 install - doesn't include crapware:

                                @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                                @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                                @Tim_G said in Fresh Win 10 install - doesn't include crapware:

                                I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

                                I honestly do not care if the crap is there or not.

                                But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.

                                Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
                                Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
                                

                                That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

                                If you don't remove the app using the bottom "-online" part, it'll be there for new users.

                                I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

                                Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

                                I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:

                                Get-AppxPackage -AllUsers | Select Name | FT
                                

                                and

                                Get-AppxProvisionedPackage -Online | Select DisplayName | FT
                                

                                Any harm removing all AppxPackages and AppxProvisionedPackages?

                                Yes don't do it.

                                Can you not do a regular expression to match everything not like that specific version of that key

                                1 Reply Last reply Reply Quote 0
                                • black3dynamiteB
                                  black3dynamite
                                  last edited by black3dynamite

                                  Windows Configuration Designer seems to be the tool that helps with removing pre-installed software.

                                  1 Reply Last reply Reply Quote 0
                                  • DashrenderD
                                    Dashrender
                                    last edited by

                                    So @JaredBusch claimed that using the registry entry listed in the first post would prevent the crap from coming back in 1703, but I couldn't get the same results.

                                    Today while creating a new image again, I noticed that the account created during logon had most, if not all of the crap, in spite of the registry key, but now I'm noting a followup user logon to the system does not have the crapware listed in the start menu.

                                    0_1499108753903_1703.jpg

                                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                                    • JaredBuschJ
                                      JaredBusch @Dashrender
                                      last edited by JaredBusch

                                      @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                                      So @JaredBusch claimed that using the registry entry listed in the first post would prevent the crap from coming back in 1703, but I couldn't get the same results.

                                      Today while creating a new image again, I noticed that the account created during logon had most, if not all of the crap, in spite of the registry key, but now I'm noting a followup user logon to the system does not have the crapware listed in the start menu.

                                      I am not claiming shit. I clearly documented it.

                                      I expect you problem is because the "crap" you are seeing is not part of the items restricted. I showed a screen shot right there in post 33.
                                      https://mangolassi.it/topic/8691/fresh-win-10-install-doesn-t-include-crapware/33

                                      DashrenderD 1 Reply Last reply Reply Quote 0
                                      • DashrenderD
                                        Dashrender @JaredBusch
                                        last edited by

                                        @JaredBusch said in Fresh Win 10 install - doesn't include crapware:

                                        @Dashrender said in Fresh Win 10 install - doesn't include crapware:

                                        So @JaredBusch claimed that using the registry entry listed in the first post would prevent the crap from coming back in 1703, but I couldn't get the same results.

                                        Today while creating a new image again, I noticed that the account created during logon had most, if not all of the crap, in spite of the registry key, but now I'm noting a followup user logon to the system does not have the crapware listed in the start menu.

                                        I am not claiming shit. I clearly documented it.

                                        I expect you problem is because the "crap" you are seeing is not part of the items restricted. I showed a screen shot right there in post 33.
                                        https://mangolassi.it/topic/8691/fresh-win-10-install-doesn-t-include-crapware/33

                                        FFS - I was saying you appeared to be right, geez!

                                        1 Reply Last reply Reply Quote 0
                                        • DashrenderD
                                          Dashrender
                                          last edited by Dashrender

                                          Here is the first profile picture.

                                          Notice the crap. (I built the machine with no network connection, put the reg key in (saw the arrows), rebooted, then logged in as this user again - installed my apps - then plugged into the network and got updates, added second user, and logged in as them - saw cleaner start menu)

                                          0_1499109525955_1703-2.jpg

                                          1 Reply Last reply Reply Quote 0
                                          • JaredBuschJ
                                            JaredBusch
                                            last edited by

                                            The image I posted in post 22 shows what it looked like after getting online and doing updates
                                            https://mangolassi.it/topic/8691/fresh-win-10-install-doesn-t-include-crapware/22
                                            Here is is again for you. The six apps on the right never downloaded or installed.
                                            https://i.imgur.com/KtnDvEn.png

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 3 / 3
                                            • First post
                                              Last post