Repair Install Windows 10 with an In-place Upgrade  


  1. Posts : 21,424
    19044.1586 - 21H2 Pro x64
       #1100

    HDL said:
    So after I would run the bat file the only thing I have is the ISO file that was used to install version 20H2. Would I use that as I have tried to in the past?
    Yes, use same ISO file which failed before - but now bat files updates registry so it won't fail
      My Computer


  2. Posts : 821
    Win 10
       #1101

    HDL said:
    So after I would run the bat file the only thing I have is the ISO file that was used to install version 20H2. Would I use that as I have tried to in the past?
    You can use the 20h2 ISO, which you tried before too.

    If you press the Windows button, type winver and press Enter, you should now see build number 19041.508.
      My Computer


  3. Posts : 21,424
    19044.1586 - 21H2 Pro x64
       #1102

    Tekkie Boy said:
    You can use the 20h2 ISO, which you tried before too.

    If you press the Windows button, type winver and press Enter, you should now see build number 19041.508.
    Do you have to reboot first to see that new winver value?
      My Computer


  4. Posts : 821
    Win 10
       #1103

    steve108 said:
    Do you have to reboot first to see that new winver value?
    I modified the script so that it rebooted when it was executed.
      My Computer


  5. HDL
    Posts : 44
    Windows 10
       #1104

    Tekkie Boy said:
    I modified the script so that it rebooted when it was executed.
    Now I am concerned again. My Windows versions is 19042.630. Does that mean the above script will not work for me or is it OK for it to go back a version or two?
      My Computer


  6. Posts : 821
    Win 10
       #1105

    So again to understand: If you have followed what I have described there:

    Repair Install Windows 10 with an In-place Upgrade

    Should the computer restart while the script is running,
    If you run the winver command after rebooting, you should see build number 19041.508.
    If not, you made a mistake.
    Only when you get 19041.508 displayed can you perform the in-place upgrade with your 20h2 ISO and keep the Files and Apps.
    I hope I have explained it more clearly now.
      My Computer


  7. HDL
    Posts : 44
    Windows 10
       #1106

    Tekkie Boy said:
    So again to understand: If you have followed what I have described there:

    Repair Install Windows 10 with an In-place Upgrade

    If the computer was restarted when the script was executed,
    If you run the winver command after rebooting, you should see build number 19041.508.
    If not, you made a mistake.
    Only when you get 19041.508 displayed can you perform the in-place upgrade with your 20h2 ISO and keep the Files and Apps.
    I hope I have explained it more clearly now.
    I did follow that page so far. However, I have not run it run it as a bat file yet. I wanted to make sure since my version number is more recent than what the bat file will make it, is it still OK to run it on a newer version? Will the script take it back to version 19041.508 even though it is running the script on a newer version. Thanks.
      My Computer


  8. Posts : 821
    Win 10
       #1107

    Seems I didn't really understand your question. Sorry

    Yes, it is fine if you run it if your version is higher and newer.
    The script is designed so that it always enters version 19041.508 in the registry.
    The script does not check the existing version either, it only change the number.
      My Computer


  9. Posts : 24,602
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #1108

    HDL said:
    ...is it still OK to run it on a newer version? Will the script take it back to version 19041.508 even though it is running the script on a newer version. Thanks.

    The problem that prevents you keeping files and apps when doing an in-place upgrade on a 20H2 machine with a 20H2 ISO is that Setup gets the wrong version from the registry. It thinks (erroneously) that you are attempting to perform a downgrade.

    The script makes your system report a version that is lower than the 20H2 ISO, so it lets you keep files and apps. The version number in the registry plays no further part after this, so it doesn't matter if it is lower than your actual installed version. Once the upgrade completes it will have written the correct new values into the registry.

    In a week or so this will all be academic, there's already a fix for this in build 19042.661 for the Insider preview ring which should be rolled out as an optional update shortly.
      My Computers


  10. HDL
    Posts : 44
    Windows 10
       #1109

    Tekkie Boy said:
    Seems I didn't really understand your question. Sorry

    Yes, it is fine if you run it if your version is higher and newer.
    The script is designed so that it always enters version 19041.508 in the registry.
    The script does not check the existing version either, it only change the number.
    Thank you for the answer.

    - - - Updated - - -

    Bree said:
    The problem that prevents you keeping files and apps when doing an in-place upgrade on a 20H2 machine with a 20H2 ISO is that Setup gets the wrong version from the registry. It thinks (erroneously) that you are attempting to perform a downgrade.

    The script makes your system report a version that is lower than the 20H2 ISO, so it lets you keep files and apps. The version number in the registry plays no further part after this, so it doesn't matter if it is lower than your actual installed version. Once the upgrade completes it will have written the correct new values into the registry.

    In a week or so this will all be academic, there's already a fix for this in build 19042.661 for the Insider preview ring which should be rolled out as an optional update shortly.
    Thanks for that information.

    - - - Updated - - -

    Tekkie Boy said:
    Seems I didn't really understand your question. Sorry

    Yes, it is fine if you run it if your version is higher and newer.
    The script is designed so that it always enters version 19041.508 in the registry.
    The script does not check the existing version either, it only change the number.
    Well I ran the bat file and it is re-installing the latest build of version 20H2, I believe. I am probably still going to have to run a repair, which is what I had wanted to do, after it is done updating. I hope it lets me do it this time but I won't know for a few hours from now.

    - - - Updated - - -

    Well I went through running that bat file. I then used the ISO file and the only option was to re-install Windows 10 version 20H2 and it re-installed the exact same version I had prior to doing all this. Consequentially I still have the same problem, which is why a MS technician said I needed to run a Repair. I still cannot run a repair and keep my apps and files.

    So the problem seems to be the machine cannot start the Peer name resolution Protocol, Peer networking Grouping, or the Peer Networking Identity Manager, all of which are supposed to be set to Automatic. I get an error message saying: Windows could not access the Peer name resolution protocol service on local computer. Error code: 0x80630203: Unable to access a key. The message for Peer networking Group is: Windows could not start the Peer networking Group on local computer. The error code is: 1069: The dependency service or group failed to start. Peer Networking Identity manager is the only one of the 3 Peer services that is running. Since I can't run a Repair, not sure that would fix it anyhow, how can I get the two Peer services to run?
      My Computer


 

Tutorial Categories

Repair Install Windows 10 with an In-place Upgrade Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  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 19:08.
Find Us




Windows 10 Forums