Windows 10 start menu after removing apps

[ns-dr6figures]

Greetings, awesome people!

 

I work for a school and we are making the move to Windows 10 for the Fall semester. I have built a reference image (on ver 1511), and things, for the most part, are working well. Except for one thing:

 

I have removed most of the default store apps/metro apps/bundled apps. When I do this before sysprep, sysprep fails. When I sysprep the image and remove the apps after the fact (using PowerShell while logged in as the local administrator), the apps are definitely gone and the start menu looks exactly the way I want it to for the local admin. If I log in as any other user, I get a series of blank colorful tiles at the bottom of the menu in a group called "Other" and a list of the names of the apps that have been removed. Clicking on these does nothing as nothing launches. I have also verified that the apps are gone using PowerShell.

 

Has anyone else had this issue? And, if so, what did you do to remediate it? I have tried many suggestions, and none have worked thus far.

 

Thank you in advance for your help; it is greatly appreciated! Here is a picture of what I am talking about.

 

[xlandhenry]

Can't you use DISM to remove it from install.wim when you build the reference image?

[sted]

Can't you use DISM to remove it from install.wim when you build the reference image?

yes if you want to capture an appx less image that is i believe the only way to do it. Personally i just deploy the base install.wim with the appx's i dont want ripped out and use mdt to install any other software id normally put in a base image saves time creating an image that will be out of date in a few months when the next variant of win 10 comes out

[alfatec]

This is the best way to remove the apps:

 

I use slightly different method. I edit the install.wim from the Windows 10 edu 1511 iso and remove the default apps, just leaving photo's and calculator. Then rebuild iso and make bootable DVD. Here is the link:https://gallery.technet.microsoft.co...DBJFGQV46sng)(). Once you build your reference image go to gpedit.msc and follow these instructions to get rid of the Microsoft customer experience apps,

like Candy Crush, Twitter etc. https://blogs.technet.microsoft.com/...turn-them-off/. Now when you sysprep and redploy your image no more annoying apps apart from the ones you want.

[dblight]

https://gallery.technet.microsoft.co...DBJFGQV46sng)(). https://blogs.technet.microsoft.com/...turn-them-off/.

 

These links are invalid..........

[alfatec]

https://blogs.technet.microsoft.com/mniehaus/2015/11/23/seeing-extra-apps-turn-them-off/

https://gallery.technet.microsoft.com/Removing-Built-in-apps-65dc387b?tduid=(569e0478750b11eef92bc61924d27191)(256380)(2459594)(TnL5HPStwNw-zWYNrEBXJwDBJFGQV46sng)()

Edited May 23, 2016 by alfatec

[dblight]

Then rebuild iso and make bootable DVD.

 

Just out of interest how are you rebuilding the iso? I have extracted the install.wim from the ISO but obviously cannot copy it back in......

[sted]

Just out of interest how are you rebuilding the iso? I have extracted the install.wim from the ISO but obviously cannot copy it back in......

just create a pen drive to boot from then you can just swap the files over

[alfatec]

You need to extract all the files from the ISO. I normally mount the ISO then copy all the files into a new folder. Amend the install.wim file then copy it back and overwrite the one that is there. I then use img-burn (a free DVD maker) to

make a bootable DVD or USB pen etc. I use this on build 1511 and have also used it on the latest anniversary update build.

[Arthur]

Just out of interest how are you rebuilding the iso? I have extracted the install.wim from the ISO but obviously cannot copy it back in......

I use oscdimg.exe from the Windows 10 ADK.

 

@echo off
SET SOURCE=en_windows_10_education_version_1511_updated_apr_2016_x64_dvd_8712927
SET LABEL=J_CEDA_X64FRE_EN-US_DV5

oscdimg.exe -h -m -o -u1 -udfver102 -bootdata:2#p0,e,b.\%SOURCE%\boot\etfsboot.com#pEF,e,b.\%SOURCE%\efi\microsoft\boot\efisys.bin -l%LABEL% .\%SOURCE% .\%SOURCE%.iso

 

^ This will create an ISO that is bootable on standard and UEFI-based PCs for 64-bit versions of Windows. For 32-bit Windows the oscdimg command is a bit simpler...

 

oscdimg.exe -h -m -o -u1 -udfver102 -b.\%SOURCE%\boot\etfsboot.com -l%LABEL% .\%SOURCE% .\%SOURCE%.iso

Edited May 23, 2016 by Arthur