Windows 10 - Start menu freezing after feature update

[Avaryan]

This is not a FOG issue, but hoping someone might know something.

The image I build and deployed this summer was Windows 10 Enterprise Build 1607. A few weeks back our machines started updating to Build 1703.

This is only affecting users who did not have a profile on the PC prior to the update. On these machines the Start menu freezes, especially if you attempt to type/search. Some applications also won’t load or become unresponsive while loading.

I’m thinking it may have something to do with AppxPackages and/or AppxProvisionedPackages that were removed on the original image. After the Build 1703 update, many (maybe all) of the AppxPackages and AppxProvisionedPackages that I had removed were restored… which was really irritating.

[x23piracy]

Hi,

i always found a solution here, even if i tried multiple of the solutions, it worked afterwards…
You may need to translate the website in to your mother tongue:

https://www.deskmodder.de/wiki/index.php?title=Startmenü_reparieren_Windows_10

You should first try to delete the following file and folder:

%userprofile%\AppData\Local\Mircosoft\Windows\UsrClass.dat 
%userprofile%\AppData\Local\TileLayerDatabase\Database

Regards X23

[Avaryan]

@x23piracy Thanks. There was some useful information on there.

[Sebastian Roth]

@Avaryan Shall we mark this solved then?

[Avaryan]

In case anyone else experience this issue, we seem to have a solution. Something corrupted the default user profile during the Feature Update from Build 1607 to Build 1703.

The following PowerShell commands took care of the issue:

Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse 

This solves the issues for any new profiles, but profiles created after the Feature Update will need to be deleted.

This can be marked as solved now.

[Avaryan]

Better fix:

The following PowerShell snippet appears to fix the previously reported issues that appeared after the Feature Update to Build 1703.

# Removes WebCache and INetCache folders from Default Profile.
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse

$Users = (Get-ChildItem -Path "$env:SystemDrive\Users").FullName

# Deletes WebCache and INetCache on all non-hidden users.
ForEach($User in $Users) {
    Remove-Item -Path $User\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse -ErrorAction SilentlyContinue
    Remove-Item -Path $User\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse -ErrorAction SilentlyContinue
} 

This fixes it for all new and existing user profiles.

[x23piracy]

@avaryan said in Windows 10 - Start menu freezing after feature update:

In case anyone else experience this issue, we seem to have a solution. Something corrupted the default user profile during the Feature Update from Build 1607 to Build 1703.

The following PowerShell commands took care of the issue:

Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse 

This solves the issues for any new profiles, but profiles created after the Feature Update will need to be deleted.

This can be marked as solved now.

Hi,

this only happens with Windows 10 1703 when you use “copyprofile” in unattend.xml, if so and if you want to stick with copyprofile (like me) you have to delete the mentioned folders but you miss a file that has also been deleted, let me have a look for it…

Found it back, look at this thread, what you found was mentioned before (read the complete thread!):
https://forums.fogproject.org/topic/10210/windows-10-1703-image-with-strange-issue/18

rd /S /Q "C:\Users\Default\AppData\LocalLow"
rd /S /Q "C:\users\Default\AppData\Local\Microsoft\Windows\WebCache"
rd /S /Q "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache"
del /F "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat"

I trigger that delete lines with setupcomplete.cmd

Microsoft changed the copyprofile behaviour, you need to know how to handle it if you still use it.

Regards X23

[Avaryan]

I’ve seen the article where those additional files were listed; however, they were not present on our systems so they were not included in the fix.

I deployed the solution posted above via SCCM to all Windows 10 systems and it’s solved our issues.

[Twilems]

@Avaryan do i have to put this script in a specified folder? Or is it just run this script and it’s fixed?

The following PowerShell snippet appears to fix the previously reported issues that appeared after the Feature Update to Build 1703.

# Removes WebCache and INetCache folders from Default Profile.
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse

$Users = (Get-ChildItem -Path "$env:SystemDrive\Users").FullName

# Deletes WebCache and INetCache on all non-hidden users.
ForEach($User in $Users) {
    Remove-Item -Path $User\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse -ErrorAction SilentlyContinue
    Remove-Item -Path $User\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse -ErrorAction SilentlyContinue
}

[Avaryan]

@twilems Just run it. It will fix the issue for all users.

[Twilems]

@avaryan Is this also working for version 1709?

[Avaryan]

@twilems No idea. If the cause is the same, then probably.