No Start Menu on Initial Logon

[Joanne]

So my current Windows 10 image is great - except for one thing...

 

When a user logs onto the machine for the first time, the start menu will not work.

 

If they log off and on again, it works fine.

 

I have a default user profile which sets what the start menu should be. When the user logs on for the second time it works perfectly.

 

 

Anyone come across this? Should I just start again?

[NokiX]

We also experience this issue however we found the start menu doesn't function at all for that user regardless of how many times they relog onto the machine. I believe it's down to the default domain policy however I have not yet managed to track down the exact cause as of yet. I would also like to see if anyone has experienced the problem as we would prefer to start using windows 10 as soon as some of the bugs we have are ironed out.

[sted]

We also experience this issue however we found the start menu doesn't function at all for that user regardless of how many times they relog onto the machine. I believe it's down to the default domain policy however I have not yet managed to track down the exact cause as of yet. I would also like to see if anyone has experienced the problem as we would prefer to start using windows 10 as soon as some of the bugs we have are ironed out.

 

I THINK that can be down to applocker if you have an applocker policy try it on a pc that hasn't got that applied

[Joanne]

I've got applocker active on this image....

 

OK on my machine - no applocker, the pupil account has normal start menu behavior.

Edited February 2, 2016 by Joanne

[Michael]

You're right that AppLocker can have a negative impact on the Start Menu, however I wonder if it's linked/related to the Application Identity service?

 

If you're still struggling, there's always Classic Shell which you can read about here

 

Either deploy to existing Windows 10 devices, or you can include it on the image from the start.

[Joanne]

I don't have any existing devices luckily. I'm in the testing phase. I don't really want to use classic shell. Might have to un-use applocker and take a deep breath and powershell it.

[Michael]

I'm not entirely convinced your issue is AppLocker related, as I'd expected the same behaviour to be there on the 2nd, 3rd, 4th logon etc... as well.

 

I can understand the reluctance to use a third party application on a key part of the OS, but since deploying Classic Shell, problems have gone right down. Logging off, Shutting down and navigating to Explorer are all easier and more straight forward. Customising and changing the Start Menu is also comparatively easy and is without a doubt more consistent.

 

Which build of Windows 10 are you using - 10240 or 10586?

[Joanne]

Using Education 1151... Just gonna check VLSC now and see if there is a newer version...

[Michael]

Build 1511 is 10586 (same thing), or to be precise it's 10586.71 at the time of writing, with the latest patch.

 

If you run 'winver' it'll tell you precisely.

[Joanne]

So it's got nothing to do with flavour then? Is Education the same as Pro?

 

Test machine is reporting 10586.71 so fully up to date.

Edited February 3, 2016 by Joanne

[Michael]

There are obviously some differences between Home, Pro, Enterprise and Education, however the Start Menu is identical in its functionality. The Enterprise version has less Apps as standard, but this still isn't going to change how it performs. It's just unfortunate that Microsoft (as yet) haven't fully addressed all Start Menu issues.

 

The next big build, codename Redstone is due out in the summer or autumn 2016, so still a long way off.

[Joanne]

I'm gonna build another image and see what happens. Doesn't normally take too long.... o.O

 

If it does the same thing I know it's an issue with the OS! I'll then try the classic shell.

[Michael]

I'm gonna build another image and see what happens. Doesn't normally take too long.... o.O

 

If it does the same thing I know it's an issue with the OS! I'll then try the classic shell.

 

Goodo, glad you're not writing it off entirely

[jmak]

So it's got nothing to do with flavour then? Is Education the same as Pro?

 

Test machine is reporting 10586.71 so fully up to date.

Education is closest to Enterprise version - we no longer get the Enterprise flavour with EES.

[Joanne]

Education is closest to Enterprise version - we no longer get the Enterprise flavour with EES.

 

I do! Maybe I asked nicely. Had to ring them up to get all my KMS keys.... not that I've got VA services fully running yet!!

[Michael]

Other considerations (when it comes to Classic Shell) - the Windows 10 Start context menu can't be removed/hidden via GPO. The only way is to remove settings from within the default profile which then applies to all logging onto that computer.

 

Classic Shell gives you the flexibility, so when Pupils/Staff login, they see a Classic Shell context menu, whereas Domain Admins can still see the original context menu. There's nothing else out there (to the best of my knowledge), that allows you to do this.

[Joanne]

Urgh... so new image and sysprep FAILS... even though I haven't uninstalled any apps. Just unpinned them.

 

Lovely log file....

 

2016-02-11 11:08:06, Info SYSPRP ========================================================

2016-02-11 11:08:06, Info SYSPRP === Beginning of a new sysprep run ===

2016-02-11 11:08:06, Info SYSPRP ========================================================

2016-02-11 11:08:06, Info [0x0f004d] SYSPRP The time is now 2016-02-11 11:08:06

2016-02-11 11:08:06, Info [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther

2016-02-11 11:08:06, Info [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine

2016-02-11 11:08:06, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything

2016-02-11 11:08:06, Info [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...

2016-02-11 11:08:10, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.

2016-02-11 11:08:10, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3

2016-02-11 11:08:10, Info [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode

2016-02-11 11:08:10, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:08:10, Warning SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2

2016-02-11 11:08:10, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:08:10, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64

2016-02-11 11:08:10, Info [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it

2016-02-11 11:08:10, Info [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error

2016-02-11 11:08:10, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'generalize' internal providers.

2016-02-11 11:08:10, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 1

2016-02-11 11:08:10, Info [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml, and mode

2016-02-11 11:08:10, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:08:10, Warning SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2

2016-02-11 11:08:10, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:08:10, Info SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:08:10, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64

2016-02-11 11:08:10, Info [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'SysprepGeneralizeValidate' in C:\Windows\System32\AppxSysprep.dll; executing it

2016-02-11 11:08:10, Info SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.

 

2016-02-11 11:08:11, Error SYSPRP Package king.com.CandyCrushSodaSaga_1.58.400.0_x86__kgqvnymyfvs32 was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

 

2016-02-11 11:08:11, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

2016-02-11 11:08:11, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

 

2016-02-11 11:08:11, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2

2016-02-11 11:08:11, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2

2016-02-11 11:08:11, Error SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2

2016-02-11 11:08:11, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

2016-02-11 11:08:11, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

2016-02-11 11:09:55, Info [0x0f0052] SYSPRP Shutting down SysPrep log

2016-02-11 11:09:55, Info [0x0f004d] SYSPRP The time is now 2016-02-11 11:09:55

2016-02-11 11:21:31, Info SYSPRP ========================================================

2016-02-11 11:21:31, Info SYSPRP === Beginning of a new sysprep run ===

2016-02-11 11:21:31, Info SYSPRP ========================================================

2016-02-11 11:21:31, Info [0x0f004d] SYSPRP The time is now 2016-02-11 11:21:31

2016-02-11 11:21:31, Info [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther

2016-02-11 11:21:31, Info [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine

2016-02-11 11:21:31, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything

2016-02-11 11:21:31, Info [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...

2016-02-11 11:21:34, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.

2016-02-11 11:21:34, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3

2016-02-11 11:21:34, Info [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode

2016-02-11 11:21:34, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:21:34, Warning SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2

2016-02-11 11:21:34, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:21:34, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64

2016-02-11 11:21:34, Info [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it

2016-02-11 11:21:34, Info [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error

2016-02-11 11:21:34, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'generalize' internal providers.

2016-02-11 11:21:34, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 1

2016-02-11 11:21:34, Info [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml, and mode

2016-02-11 11:21:34, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep

2016-02-11 11:21:34, Warning SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2

2016-02-11 11:21:34, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:21:34, Info SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

2016-02-11 11:21:34, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64

2016-02-11 11:21:34, Info [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'SysprepGeneralizeValidate' in C:\Windows\System32\AppxSysprep.dll; executing it

2016-02-11 11:21:34, Info SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.

 

2016-02-11 11:21:35, Error SYSPRP Package king.com.CandyCrushSodaSaga_1.58.400.0_x86__kgqvnymyfvs32 was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

 

2016-02-11 11:21:35, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

2016-02-11 11:21:35, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

 

2016-02-11 11:21:35, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2

2016-02-11 11:21:35, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2

2016-02-11 11:21:35, Error SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2

2016-02-11 11:21:35, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

2016-02-11 11:21:35, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

2016-02-11 11:21:56, Info [0x0f0052] SYSPRP Shutting down SysPrep log

2016-02-11 11:21:56, Info [0x0f004d] SYSPRP The time is now 2016-02-11 11:21:56

[Michael]

Unpinning shouldn't cause Sysprep issues, but removing Apps probably will. On all images, I use AppLocker to restrict certain Apps running, but then in combination with Classic Shell, Apps aren't even visible on the Start Menu, only what I specify.

 

The source is most likely linked to:

 

2016-02-11 11:08:11, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

2016-02-11 11:08:11, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

 

The new February 2016 update brings the build to 10586.104, which you may want to try.

[Joanne]

sniffle....

 

 

A wild idea appears....

[Michael]

You're having little luck with this aren't you? Sometimes leaving it and coming back to it, things magically fix themselves.

[Joanne]

I tried activating Windows - no dice. Removed it from the domain - no dice.

 

Might load the "working" image, edit it, perhaps put classic shell on and see what happens.

[Joanne]

Right. Removed candy crush and twitter via powershell command and it seems to be sysprepping now. Feel like I've missed something. Like my default user config.... hmmm... we shall see!

[Arthur]

I've got applocker active on this image....

I wonder if it's linked/related to the Application Identity service?

Packaged App Rules issue?

 

Windows 10 Start Menu Does Not Work with AppLocker

 

In my lab I had newly built Windows 10 Enterprise PC’s that are joined to a domain. Before they join the domain all apps are functioning fine, however, as soon as one of them joins the domain ALL the Windows 10 packaged apps stop working even the start menu (Cortana) doesn’t work and the Edge browser does not appear on the taskbar.

 

Now I know I have some AppLocker GPO’s in the environment that prevent users from running applications under their user folder (C:\User\Username) but that does not explain why these apps are not running as they are not run from one of these locations.

 

Looking at the event logs, the AppLocker event log reads: “No packaged apps can be executed while EXE rules are being enforced and no packaged app rules have been configured”

 

Under Windows 8.x and 10, the new applications require new AppLocker rules called Packaged App Rules. These rules target the new Modern UI style apps. If you enable AppLocker with simple .exe based rules, Windows will automatically disable ALL modern apps unless unlocked by specific AppLocker rules.

[Michael]

My only reservation if it was a mis-configuration, is it would happen at every logon, not just first logon.

[MMPS]

We also experience this issue however we found the start menu doesn't function at all for that user regardless of how many times they relog onto the machine. I believe it's down to the default domain policy however I have not yet managed to track down the exact cause as of yet. I would also like to see if anyone has experienced the problem as we would prefer to start using windows 10 as soon as some of the bugs we have are ironed out.

 

We experienced the same thing on our laptops, using Win 10 Pro build 10586. So I don't think this is related to Applocker or the Win 10 Edu release. I'm using classic shell as a temporary fix until this is resolved, and so far had no issues. Unfortunately, without full screen mode, classic shell isn't an option for our tablets, so they'll have to stick with 8.1 for now.