Start menu in Windows 10 PRO after installing Creator update 1703
The installation is on a network running server 2008 R2. The workstations are running Windows 10 Pro. They were all running the anniversary update. I have installed the Creator update 1703, and most of the start menu now is not functional. The original icons have been replaced with a vertical arrow point to a solid line
I have ran sfc /scannow, and there were no issues to resolve. start-menu.jpg
Correct, that icon is a placeholder for apps that have not been downloaded, yet. MS adds several of such apps to clean installations and they are installed after logon on internet connected computers. On computers that remain offline (because the user/company wants it), these icons remain - what a nuisance.
John
I am running 1703 15063.138 without issue.
If the icons do not repair themselves after internet connection (and SFC did not fix the issue), try a Windows 10 Repair Install from the Media Creation Link. Nothing need be lost.
Try one machine without your 3rd party Anti Virus. Uninstall it and let Windows Defender take over temporarily. SEP 14 MP1 newest does not work with Version 1703.
Shaun Vermaak
If you are not using any store apps in your environment, you can use this command to remove all (similar to LTSB)
I have SEP 14 MP1 release 2394 and it seems to work fine with 1703. On computers not on a server, the icons in the start menu do not change. The ones on the computers on a domain running under server 2008 R2 have changed. The computers connect to the internet fine, and can access Microsoft for updates.
I have tried uninstalling SEP by using the cleanwipe tool, and then installing 1703, and the results are the same. The icons are only place holders for most of the previous icons.
Would removing the package remove the start menu, or just the non functioning icons
Give "Read" permission to "All Application Package" group on the HKEY_CLASSES_ROOT
Wilf
ASKER
When the new computers were installed last fall [with version 1607], an admin user was created in order to log on prior to joining a domain.
If I log on to the admin [non domain] account, the start menu is normal. I have removed one computer from the domain [joined workgroup] and it is presently installing 1703. I will see what it does when it rejoins the domain.
Any suggestions to get the menu back under a domain installation?
Please let us know after re-joining . It may be an issue between Windows 10 so new and Server 2008 so old.
Wilf
ASKER
I have rejoined from Workgroup to Domain. The menu still has the placeholders when I log on.
It appears that the menu works fine with the user logged on to the computer on a local account.
It appears to work fine when the computer is not connected to a domain
It worked fine in 1607
The menu has place holders in 1703 once the 2008 R2 domain is joined regardless if it was installed while on the domain or while as a stand alone workgroup computer.
I have the opportunity to try a unit on a server 2012 R2 domain. The only difference is that the server 2012 domain is using SEP 12 MP6 and one unit with MP7.
I hope to make that test this evening, so will post those results also
Wilf
ASKER
"Read" permission to "All Application Package" group on the HKEY_CLASSES_ROOT is identical when connected to the domain or workgroup in terms of the Read permission being checked
SEP V12 is not compatible with Windows 10 V1703 . You need to try the very newest version of SEP V 14.0.0 MP1. SEP can cause permission issues internally with Windows 10 V1703.
Wilf
ASKER
I was able to install SEP 12.1.6MP7 on the anniversary update, then 1703 seemed to install just fine. I haven't got it on the domain yet.
Would you suggest I roll back until SEP 14 MP1 2349 is installed?
There is no indication AV software is the culprit, yet. David has told you why the icons look like that and suggested to redownload them manually. Was that even tried? Maybe store access is the problem.
Wilf
ASKER
I will try again. The only time the icons are messed up is when the computer is joined to a network. If logged on as a local computer, they are fine, log out, and log back in on the domain, and many are as shown in the screenshot.
John
Try rolling back to Version 1607 and see if icons work on your server.
That is no icon error, but an indication that apps are about to be reinstalled, but the process does not finish. Is there a domain gpo denying access to the store?
Wilf
ASKER
There are no gpo changes from the original server installation. The icons were present in the first release of Windows 10 [only on a couple of machines at that time]. The icons work fine if rolled back to 1607, or on 1703 if logged on as a local user to the machine instead of logged on as a domain user
As McKnife indicated, David suggested re-installing the apps first out of the gate. The disjoin was accomplished on two scenarios - one just log on as a local user and not a domain user, and all icons and apps are present. The other scenario was to actually leave the domain and join work group. This also had all icons present.
Downloading the apps from the store installed ok, and I was able to pin the icon to the start menu.
Final result was to unpin the unidentified ones, pin the ones that seemed to be needed and add other apps as required.
I have found the same situation with server 2012 R2 and SEP 12.1.6MP6 or MP7 behave the same