Move users folder with sysprep NOT WORKING. Help!


  1. Posts : 3
    Vista
       #1

    Move users folder with sysprep NOT WORKING. Help!


    Getting fed up with this. Fails every single time with the same error that the file could not parse.

    I've followed the tutorial on this site TO THE LETTER and it still won't work. I've tried the control-shift-f3 route which hasn't actually worked for months (always fails with he same error, something has been changed by MS) and on a clean install which fails with the exact same error.

    Tried creating new installation media which made zero difference.

    Is there a fault with the code used in the tutorial?
      My Computer


  2. Posts : 42,985
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    As you've not cited the tutorial, I presume it's this one.
    Move Users Folder Location in Windows 10

    Perhaps @Kari can help you.
      My Computers


  3. Posts : 3
    Vista
    Thread Starter
       #3

    That's the one, thanks. It worked well before then wouldn't work during install now it fails both ways.
      My Computer


  4. Posts : 42,985
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    You could post 1 comment under that tutorial with a link to this thread asking for help in this thread. As you can see I've mentioned Kari, the author, for you above.
      My Computers


  5. Posts : 17,661
    Windows 10 Pro
       #5

    fuzzy10 said:
    Getting fed up with this. Fails every single time with the same error that the file could not parse.
    Sysprep not being able to parse an answer file relocating Users folder means, without an exception, one of two things:
    1. The answer file has syntax errors, is written wrong
    2. The drive where Users folder should be relocated is not available, present in system, when Windows setup runs

    As I mentioned, there are no exceptions. Your issue is one of those two.

    fuzzy10 said:
    I've followed the tutorial on this site TO THE LETTER and it still won't work. I've tried the control-shift-f3 route which hasn't actually worked for months (always fails with he same error, something has been changed by MS) and on a clean install which fails with the exact same error.
    Booting to Audit Mode with CTRL + SHIFT + F3 from OOBE region selection screen works without issues. Always.

    fuzzy10 said:
    Is there a fault with the code used in the tutorial?
    No.

    Kari
      My Computer


  6. Posts : 3
    Vista
    Thread Starter
       #6

    Kari said:
    Sysprep not being able to parse an answer file relocating Users folder means, without an exception, one of two things:
    1. The answer file has syntax errors, is written wrong
    2. The drive where Users folder should be relocated is not available, present in system, when Windows setup runs

    As I mentioned, there are no exceptions. Your issue is one of those two.



    Booting to Audit Mode with CTRL + SHIFT + F3 from OOBE region selection screen works without issues. Always.



    No.

    Kari
    The drive is present, checked and re-checked along with the drive letter.

    The code is copied, pasted and compared letter for letter. Be aware that moving the user file during install does not appear to work with update 21H2. It fails every single time and does it on multiple PC's which display the exact same error.

    This isn't a drive issue, they are erased before each re-try and the relocate file moved back. MS must have changed something.

    - - - Updated - - -
    @Kari

    I would like you to explain WHERE the fault is here? This is after changing the target drive letters to Q to ensure it wasn't conflicting. It is exactly the same if it is left as D. I get this exact error no matter what I try.

    Move users folder with sysprep NOT WORKING. Help!-dscn0874.jpg

    - - - Updated - - -

    Are you going to respond at all @Kari ?

    - - - Updated - - -

    Right @Kari . This is a coding error with OOBE and NOT a drive error. I know this because IT STARTS TO COPY THE FILES BEFORE FAILING. I get the user file, administrator file and the 3D file copied. At this point it fails.

    I suggest that you check and check again that MS haven't altered something in the install media that blocks the user file from being moved.

    It doesn't work moving during install OR on a fresh install. Both give the exact same error message as posted.

    - - - Updated - - -

    There is an issue with this unattend file in 21H2. It works perfectly on version 1903. I think some testing needs to be done to find out where the issue is.

    I strongly suspect the MS *have* changed something to stop this from working hence the OOBE error.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:16.
Find Us




Windows 10 Forums