[1709, fcu] Start Menu issues

[clareq]

Sorry to bring up this old chestnut again. I'm just starting the development of Windows 10 here, and a decision has been made to go with the edu branch. At my last school I used LTSB, so I'm having to re-invent the wheel.

 

So, I've migrated SCCM from 2012 to 1709, on new hardware. My old Win 7 deployments work fine, so on to Win 10. My thought was, with a new version coming out ever 6 months, I was better using the install.wim off the disk, and deploy the applications in the task sequence, rather than the fat image I used with 7. So, start small - I have a test TS with the install wim, an unattend.xml to set the language etc, install drivers and add to the domain. I then added Office 2016 as a single application. The TS works fine, I log onto it with my admin account, and the start menu doesn't work. I've seen this before with roaming profiles, but my account uses local profiles. I logged on as local admin and tried deleting the profile anyway, but I still had no start menu when I logged back on.

 

Any ideas?

[clareq]

Anyone?

[Patrick]

What do the logs say? When you say it isn't working do you mean it doesn't work completely or redirected start menu doesn't work? If it's not working at all, does your TS strip out any apps? If yes try running this in powershell and see if it fixes it

 

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Edited February 20, 2018 by Patrick

[clareq]

It's not working at all - start menu, search and cortana. My TS at the moment is basic - I partition the disk, apply the OS from the original install.wim, apply Windows settings to add UserName and enable the local admin account, apply network settings to add it to the domain and drop it into an OU - which has no GPO's assigned to it, apply drivers, install sccm client and add Office and Sophos. I think I've tried that script, but I'll give it another go. I'm also going to try disabling Sophos.

[jonbd]

You don't use Applocker do you? I had the same issue when I first started testing Windows 10, but it was because I hadn't created default Applocker rules for packaged apps.

[clareq]

No applocker rules in place - no GPO's at all at the moment.

[Patrick]

What happens if you create a new local user, does it work then? Powershell command for that:

 

net user NewUsername NewPassword /add

Edited February 20, 2018 by Patrick

[clareq]

A new local user sees the same issue.

[Patrick]

I suppose you could try redeploying but taking out a piece of the sequence at a time to rule things out, only thing i can suggest to narrow it down.

[clareq]

That's exactly what I am doing. I have a task sequence now that loads windows and drivers and adds to a workgroup. Nothing else.

[RLR]

I had a similar issue. I imaged about 20 laptops all with the same image. It seemed about half of them wouldn't let users open the start menu where the half it was fine. I spent a few days trying to figure out what it might have been. Tried removing GPO's one at a time, changing registry and any other ideas I found on Google. I never found out why this happened but I re-imaged them all with MDT in the same way you are (my install.wim has had most of the built in window apps removed). I'm also using a new command to set a specific Start Menu and Task Bar:

 

PowerShell.exe -Command Import-StartLayout -LayoutPath \\Network\Path\to\StartLayout.xml -MountPath c:\

 

The startlayout.xml:

https://drive.google.com/file/d/1W0pLGecpAOx1_BzXavCwPEL__FYvUlYM/view?usp=sharing

 

After imaging all the laptops again with this it seems to be working.

 

Another odd thing I found is I used the same imaging task sequence for Dell Computers and the HP Laptops. The HP laptops are the only machines that had the start menu issue.

 

I'm wondering if it has something to do with windows app being removed from the wim file. Have you done this?

Edited February 20, 2018 by RLR

[clareq]

I've not removed any apps from the wim - I have slipstreamed updates, but only after the issue occurred.

 

UPDATE - it's Sophos. If I don't add Sophos I have a start menu.

[Steve21]

I thought they'd fixed it but there's a known bug with Sophos breaking start menus unless you disable one of the new 1709 options.

 

You had to disable the "user my sign in info" blah blah option to bypass the issue, might be worth a test on one locally that's broken. (under settings sign in options etc)

 

Steve

[RLR]

Ah, that's good to know. We use sophos which might explain why my issue was so intermittent.

[clareq]

And the fix - a GPO to turn off Defender. There seems to be a conflict between them.

[gch]

Thanks, we use Sophos so it's good to know in advance of our migration.

[mullet_man]

Hi clareq - glad you've fixed your start menu. We've all had many fights with it for the last few years.

 

I create a "slim" image now using hyperv which has just CS6 and Office and then I used SCCM to blast out the rest. Seems to have worked well with 1703 and 1709 so am going to keep with it.

 

There is a task sequence step that you can use to delete the apps you don't during deployment which seems the best route so you keep your image unaltered.