• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Windows 10 - Start menu freezing after feature update

Scheduled Pinned Locked Moved Unsolved
Windows Problems
4
12
3.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • X
    x23piracy
    last edited by x23piracy Nov 20, 2017, 7:12 AM Nov 20, 2017, 1:08 PM

    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

    ║▌║█║▌│║▌║▌█

    A 1 Reply Last reply Nov 22, 2017, 1:53 PM Reply Quote 0
    • A
      Avaryan @x23piracy
      last edited by Avaryan Nov 30, 2017, 11:45 AM Nov 22, 2017, 1:53 PM

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

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Nov 22, 2017, 9:16 PM

        @Avaryan Shall we mark this solved then?

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • A
          Avaryan
          last edited by Nov 30, 2017, 5:51 PM

          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.

          X 1 Reply Last reply Nov 30, 2017, 10:08 PM Reply Quote 0
          • A
            Avaryan
            last edited by Nov 30, 2017, 8:00 PM

            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.

            T 1 Reply Last reply Dec 19, 2017, 12:05 PM Reply Quote 1
            • X
              x23piracy @Avaryan
              last edited by x23piracy Nov 30, 2017, 4:12 PM Nov 30, 2017, 10:08 PM

              @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

              ║▌║█║▌│║▌║▌█

              1 Reply Last reply Reply Quote 1
              • A
                Avaryan
                last edited by Dec 1, 2017, 6:23 PM

                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.

                1 Reply Last reply Reply Quote 1
                • T
                  Twilems @Avaryan
                  last edited by Twilems Dec 19, 2017, 6:06 AM Dec 19, 2017, 12:05 PM

                  @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
                  }
                  
                  A 1 Reply Last reply Dec 19, 2017, 12:18 PM Reply Quote 0
                  • A
                    Avaryan @Twilems
                    last edited by Dec 19, 2017, 12:18 PM

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

                    T 1 Reply Last reply Dec 19, 2017, 12:39 PM Reply Quote 0
                    • T
                      Twilems @Avaryan
                      last edited by Dec 19, 2017, 12:39 PM

                      @avaryan Is this also working for version 1709?

                      A 1 Reply Last reply Dec 19, 2017, 12:46 PM Reply Quote 0
                      • A
                        Avaryan @Twilems
                        last edited by Dec 19, 2017, 12:46 PM

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

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post

                        124

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.4k

                        Posts
                        Copyright © 2012-2024 FOG Project