Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, November 20, 2015 1:23 AM | 1 vote
There is a lot of information online regarding this issue, but I haven't been able to find a solution yet. Long story short, I've created a mandatory profile (.v5) for Windows 10. I've got the GPO set to use the profile whenever someone logs in, however the start button and some items on the task bar are not functional. I'm running the latest build 1511, but this has been occurring since the beta and RTM.
Again, lot of info floating around but no solution. I'm wondering if this is a bug that hasn't been addressed yet.
Any ideas?
Thanks.
All replies (17)
Friday, November 20, 2015 3:57 AM ✅Answered | 2 votes
Tried this ?
Open a powershell administrator command line and run this command:
“Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}”
Or open Command Prompt as Administrator and type in the following commands:
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Monday, November 30, 2015 2:49 AM ✅Answered
Hi,
Have you used “CopyProfile = true” in Window 10 Unattend.xml? Try a clean image without any Windows update for deployment or take “CopyProfile = true” out for good measure. Though I haven’t checked in newest build of Windows 10, seems like it is a known issue in previous build.
Have a look at following thread for references
Regards,
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Friday, November 20, 2015 3:24 PM | 1 vote
No Luck. Any other suggestions?
Monday, November 23, 2015 9:09 AM | 1 vote
Hi,
This is a potential issue in Windows 10, many suggestion has been mentioned as “worked” in older thread, and I collected some of them. Please make sure all Windows update has been installed for good measure.
Try enable your UAC see if it resolve the issue. If you have policy to disable UAC in your environment, it might cause similar issue.
Try suggestions mentioned below.
Regards,
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Tuesday, November 24, 2015 11:18 AM
Hi
I have the same issue with a new 1511 image I have just created. I have a user that is create before I run sysprep, where everything is working fine. After I sysprep the user cannot access Start Menu, Search and Action Center.
If I create another user everything works. It seems like an issue with pre-installed apps. When I enter "Apps & Features" under Settings->System, it does not list a single Store app. If I enter my new user I can see all the default apps.
I have tried running the PowerShell script above, but it does not resolve the issue. Anyone that have been able to fix this issue?
Thomas | MCP | http://www.techwork.dk
Wednesday, June 8, 2016 1:05 PM
Same problem here with Windows 10 1511 LTSB. We are able to make modifications to a profile and use sysprep with copyprofile=true. This all works and newly created local account are fully functional - start menu, search all working OK. To export the profile we use the GUI window within System -> User accounts and we have tried setting the "Permitted to use" option to Everyone and Authenticated Users but it makes no difference. We upload the profile to a file share, rename ntuser.dat to ntuser.man and add .V5 to the end of the folder containing the profile. We then use GPO to configure all accounts logging on to this PC to use the saved profile.
The problem is when users logon the Start menu does not appear when clicking Start and Search is broken. You also cannot right-click on any windows within the task bar.
The closest we have been to getting it working was when we copied the default profile before doing any customization or using sysprep+copyprofile. At that point we were able to convert to mandatory profile and the Start menu did appear albeit after a slight delay of maybe 1 second. Search was still broken however.
We have tried a profile from a non-LTSB machine - no difference.
Desperately need a solution to this.
Friday, July 22, 2016 10:13 PM
Pretty much the same here Birtybasset, kept mine as vanilla as possible but still no luck...just going to try and remove all the modern apps via the three lines below to see if that changes the situation (clutching at straws though tbh):
- Get-AppxPackage | Remove-AppxPackage
- Get-AppxPackage -allusers | Remove-AppxPackage
- Get-AppXProvisionedPackage -online | Remove-AppxProvisionedPackage -online
Will update with results...
Might have to wait until 2nd of August and try then?!
Friday, July 22, 2016 10:26 PM
Apologies for not updating this thread. I got it all working eventually! When I get back in the office on Monday I'll dig out my notes and update here. Before that I opened a ticket with MS support and was less than impressed with their troubleshooting abilities. They were pretty much useless but did admit that it was a bug and that they were working to resolve it.
Removing the Apps had nothing to do with it, having said that we are running LTSB so most of the apps are already stripped-out.
Mandatory profiles are now working great for us. We get a logon time of around 15 seconds from pressing enter after password to desktop + icons, etc.
Friday, July 22, 2016 10:36 PM
No luck, just cannot get a mandatory profile working in terms of a functional start menu and search...
Monday, July 25, 2016 1:04 PM
It's all about the following registry key which seems to get locked after a profile is created and no matter what you do, you cannot edit the permissions on it so the only thing to do is delete it!
HCKU\SOFTWARE\Microsoft\Windows\CurrentVersion\DeviceAccess
From my notes:
Before running sysprep/copyprofile I deleted the following key: HCKU\SOFTWARE\Microsoft\Windows\CurrentVersion\DeviceAccess.
Ran sysprep/copyprofile, let machine reboot, logged in with newly created local user account, copied default profile to profile server SMB share, renamed to .V5 (but did not rename ntuser.dat to ntuser.man (I forgot!)), joined machine to domain, logged in with my regular domain user account, saw that start menu worked but search didn't. Logged out. Renamed ntuser.dat to ntuser.man, logged in with another domain user account and saw that start menu worked as did Search!
Give it a try...
Thursday, August 11, 2016 9:37 PM
Hello Birty, it's work fine for me! However the customizations maded in the start screend not keeps. I think that in this case we will need to set a group policity object to configure the default start screen layout.
Thank you so much for your help.
Another question.. ¿What about the DeviceAccess Key?
Greetings,
Jason Corchuelo
Tuesday, August 16, 2016 1:39 PM
I've yet to find anyone who has mandatory profiles working satisfactorily with Windows 10.
Wednesday, August 17, 2016 2:38 AM
Hello again, i want to share with you something. In one scenario the client had a Group Policy Objects that not allow to modify hives of local user accounts. However we create a lab and define and capture the template without the registry key and implemented successfully. The problem here was that the default libraries captured in spanish operating system appears now in English in customer computers. HAHAHA Definitely a little bit of bugs around this topic. I hope Microsoft solves this ASAP.
Greetings,
Tuesday, September 19, 2017 12:44 PM
Thank you so much! Oddly enough procmon didn't show any issues accessing this hive, but removing it (which is a pain in itself, taking ownership and setting permissions on all keys), our start menu is alive!
Yannick van Rooyen // Helion IT // wwww.helionit.nl
Tuesday, September 19, 2017 3:24 PM
FYI the issue is resolved in LTSB 2016.
Thursday, September 28, 2017 9:25 AM
FYI the issue is resolved in LTSB 2016.
No it's not. We have the problem and I have Windows 10 Enterprise 2016 LTSB 1607.
Start menu opens but all others than "Search" menu items are unresponsive.
None of the "Start menu repair instructions or hints" works for us. :(
Thursday, March 28, 2019 7:50 PM | 1 vote
I know this is an old post, but still relevant. BirtyBassett is on the right track here, but you can resolve it at any point. Simply download psexec.exe, run "psexec -i -s CMD", launch regedit, load up your mandatory profile, and give users permissions to the DeviceAccess key listed above.