Windows 10 - Start menu freezing after feature update
-
@x23piracy Thanks. There was some useful information on there.
-
@Avaryan Shall we mark this solved then?
-
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.
-
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.
-
@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/18rd /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
-
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.
-
@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 }
-
@twilems Just run it. It will fix the issue for all users.
-
@avaryan Is this also working for version 1709?
-
@twilems No idea. If the cause is the same, then probably.