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

Start Menu after Sysprep - non-Fog issue

Scheduled Pinned Locked Moved Solved
Windows Problems
3
5
1.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.
  • C
    Chris Shipley
    last edited by Apr 22, 2019, 7:19 PM

    This was the most appropriate forum I could find to post about this issue. I’m having trouble with an image I created and post sysprep, “search” from the Start Menu isn’t working correctly. It just gives me dots that move across the top of the search (see screenshot below). Can anyone offer some insight on this for me, or a better forum to ask about imaging windows with sysprep in general? This is a Windows 10 1803 image. There used to be a Windows 10 Start Menu Troubleshooter from Microsoft, but it appears they’ve removed that and suggest you “Reset your PC” - I’d rather not do that just now.

    Happy to hear any and all suggestions. So far I’ve tried:

    • SFC /scannow
    • Reinstalling all Win10 apps (including Cortana and Start Menu)
    • Rebuilding the search index

    I have -NOT- tried:

    • Reset My PC - this would be very painful for us right now

    alt text

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Apr 22, 2019, 9:57 PM

      @Chris-Shipley Please search the forums, I am fairly sure we had this already.

      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

      C 1 Reply Last reply Apr 23, 2019, 3:21 PM Reply Quote 0
      • X
        x23piracy
        last edited by x23piracy Apr 23, 2019, 8:56 AM Apr 23, 2019, 2:55 PM

        Hi,

        please delete the following and try again:

        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"
        

        This is only for newly created user accounts, if the account (profile) already exists you have to delete this in the specific profile, log off and on after that and try again.

        I don’t know if that helps you, sources:

        https://forums.fogproject.org/topic/10210/windows-10-1703-image-with-strange-issue
        https://forums.fogproject.org/topic/10766/windows-10-1703-delete-this-if-you-use-copyprofile-in-unattend-xml

        _Do you use “Copyprofile” within your unattend.xml? Which Win 10 Version is it? 1703, 1709, 1803, 1809 or 1903?

        Regards X23

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

        C 1 Reply Last reply Apr 23, 2019, 3:45 PM Reply Quote 1
        • C
          Chris Shipley @Sebastian Roth
          last edited by Apr 23, 2019, 3:21 PM

          @Sebastian-Roth I appreciate that, and I did try to search the forums but didn’t turn up a result. Perhaps my search was too narrow.

          @x23piracy Thank you, I’ll give this a go. It is the first time I tried copyprofile, i thought for sure it would, i don’t know, copy all the windows start menu, default file associations, shortcuts on the desktop … I may just avoid this in the future. I’m using 1803, and will report back after I give that a go and create a new user profile.

          1 Reply Last reply Reply Quote 0
          • C
            Chris Shipley @x23piracy
            last edited by Chris Shipley Apr 23, 2019, 10:29 AM Apr 23, 2019, 3:45 PM

            @x23piracy that did the trick for me, now i just need to read up on where to put that handy CMD file you wrote. thanks so much.

            For those that are doing that post deployment where a user already logged in, had to reboot in safe mode, delete the files, remove the profile from profilelist in registry, change the folder name in c:\users\USERNAME to c:\users\USERNAME.BAK, reboot, and then the user logged in again and it was good.

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

            157

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project