none
Window 1803 to 1903 upgrade error RRS feed

  • Question

  • Hello Experts,

    We are updating the windows 10 OS version from 1803 and 1809 to 1903 for 40k machines.

    70% of the machines were updated to 1903 version and rest of the machines are not updating to 1903 eventhough we have been trouble shooting with error codes as per the blogs which has given the fix.

    During trouble shooting of the failed machines the worst part is disk space issue failure machines.
    Hope we required minimum of 25 GB of free space before upgrading to 1903, but for many machines still failing due to disk space issue even though it has 40GB of free space.
    Not sure why it is getting failed, i just want to know how it was calculating the disk space and from where it was getting the disk space as a reference.

    i have tried to run the setupdiag tool to get the issue and it was showing as FOUND HARD DISK SPACE, tried the below cmd too.

    net stop wuauserv 
    net stop cryptSvc 
    net stop bits 
    net stop msiserver 
    Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 
    Ren C:\Windows\System32\catroot2 Catroot2.old 
    net start wuauserv 
    net start cryptSvc 
    net start bits 
    net start msiserve

    Kindly help to fix the issue.

    Setupact.log

    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=5
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=2
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=9
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=3
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=0xC190020E
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=0x4001E
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=17763
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=rs5_release
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=18362
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=19h1_release
    2019-07-18 14:41:09, Info                  DIAGER DiagERSetHeader:Entry
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::SetHeader:Entry
    2019-07-18 14:41:09, Info                  DIAGER IDiagER::SetHeader:Entry
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::SetHeader:Setting header=Microsoft Windows Installation encountered a problem and needs to close. We are sorry for the inconvenience
    2019-07-18 14:41:09, Info                         CDiagnosticsHelper::GetWatsonFilesToAttach: Attaching file C:\$WINDOWS.~BT\Sources\Panther\SetupAct.log
    2019-07-18 14:41:09, Info                         CDiagnosticsHelper::GetWatsonFilesToAttach: Attaching file C:\$WINDOWS.~BT\Sources\Panther\diagerr.xml
    2019-07-18 14:41:09, Info                  DIAGER DiagERAddFiles:Entry
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddFiles:Entry
    2019-07-18 14:41:09, Info                  DIAGER IDiagER::AddFiles:Entry
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddFiles:Adding file=C:\$WINDOWS.~BT\Sources\Panther\SetupAct.log
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::AddFiles:Adding file=C:\$WINDOWS.~BT\Sources\Panther\diagerr.xml
    2019-07-18 14:41:09, Info                  DIAGER DiagERSubmitEx:Entry
    2019-07-18 14:41:09, Info                  DIAGER CWfpER::Submit:Entry
    2019-07-18 14:41:11, Info                  DIAGER Watson Error Report submitted and Result=2
    2019-07-18 14:41:11, Info                  DIAGER DiagERTerminate:Entry
    2019-07-18 14:41:11, Info                  DIAGER CWfpER::~CWfpER:Entry
    2019-07-18 14:41:11, Info                  DIAGER Consent Value = HKCU\Software\Microsoft\Windows\Windows Error Reporting\Consent!WinSetupDiag02 has been cleaned out
    2019-07-18 14:41:11, Info                  DIAGER IDiagER::~IDiagER:Entry
    2019-07-18 14:41:11, Info                         Key CollectTrace is not available.
    2019-07-18 14:41:11, Info                         Copy telemetry file: source folder: C:\$WINDOWS.~BT\Sources\Panther, destination folder: C:\ProgramData\Microsoft\Diagnosis\ETLLogs
    2019-07-18 14:41:11, Info                         Copy etl files: source: C:\$WINDOWS.~BT\Sources\Panther\DlTel-Merge.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl
    2019-07-18 14:41:11, Info                         pCopyTelemetryFile: Wrote CV pf4guEjYCk+Xtf+n.6.0.0.3.20 to ETL C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl:$ETLUNIQUECVDATA
    2019-07-18 14:41:11, Info                         Diagtrack service is running
    2019-07-18 14:41:14, Info                         Successfully Forceuploaded the telemetry data.
    2019-07-18 14:41:14, Info                         Upload files successfully so we can remove all etl files.
    2019-07-18 14:41:14, Info                  SP     Closing Panther Logging
    2019-07-18 14:41:14, Info                  MOUPG  MoSetupPlatform: Setup Platform object released!
    2019-07-18 14:41:15, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [0].
    2019-07-18 14:41:15, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
    2019-07-18 14:41:16, Info                  MOUPG  Finalize: Leaving Execute Method
    2019-07-18 14:41:16, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
    2019-07-18 14:41:16, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]
    2019-07-18 14:41:16, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001]
    2019-07-18 14:41:16, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [0].
    2019-07-18 14:41:16, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
    2019-07-18 14:41:17, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [0].
    2019-07-18 14:41:17, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
    2019-07-18 14:41:17, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [0].
    2019-07-18 14:41:17, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
    2019-07-18 14:41:17, Info                  MOUPG  Signalling actions thread to shut down.
    2019-07-18 14:41:17, Info                  MOUPG  Waiting for actions thread to exit.
    2019-07-18 14:41:17, Info                  MOUPG  Actions thread has exited.
    2019-07-18 14:41:17, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
    2019-07-18 14:41:17, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]
    2019-07-18 14:41:18, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]
    2019-07-18 14:41:19, Info                  MOUPG  DlpTask: Leaving Execute Method
    2019-07-18 14:41:19, Info                  MOUPG  SetupManager::ExecuteCustomScript: Type = [0x3]
    2019-07-18 14:41:19, Info                  MOUPG  SetupManager::ExecuteCustomScript: No scripts found. Finished type [0x3]
    2019-07-18 14:41:19, Info                  MOUPG  SetupNotify::Leaving well-known error [0xC190020E] as-is for WU/Store
    2019-07-18 14:41:19, Info                  MOUPG  We are exiting in Update Setup due to compat issues. We should not clean up in this case so we can resume.
    2019-07-18 14:41:19, Info                  MOUPG  SetupNotify: Specifying extended data [0x4001E] for error [0xC190020E].
    2019-07-18 14:41:19, Info                  MOUPG  SetupHost: Reporting error event -> [0xC190020E, 0x4001E]
    2019-07-18 14:41:19, Info                  MOUPG  SetupNotify::ReportEvent - ReportSetupEvent [{B6BE66E2-E8F6-4FE3-97A4-665E2F8ACFF1}.202,0x2,0xC190020E,0x4001E,0x1]
    2019-07-18 14:41:19, Warning               MOUPG  SetupManager: In case of no cleanup, we should set the original state back.
    2019-07-18 14:41:19, Info                  MOUPG  Setup phase change: [SetupPhaseError] -> [SetupPhasePrepare]
    2019-07-18 14:41:20, Info                  MOUPG  SetupManager: FailureCount = [1]
    2019-07-18 14:41:20, Info                  MOUPG  SetupManager: Requesting cleanup level [0x0] from parent process.
    2019-07-18 14:41:20, Info                  MOUPG  SetupManager: No cleanup requested.
    2019-07-18 14:41:20, Error                 MOUPG  CSetupManager::Execute(284): Result = 0xC190020E
    2019-07-18 14:41:20, Error                 MOUPG  CSetupHost::Execute(412): Result = 0xC190020E

    And the free space of the machine is 40GB.


    THANKS SURESH M

    Tuesday, August 20, 2019 1:29 PM

All replies

  • 40 GB is okay.

    A few things to be checked:

    Remove all external storage media, such as USB drives and SD cards. Also remove any USB connected devices 
    Temporarily disable or completely uninstall any 3rd party antivirus or security program from your system.
    If you have enabled the Developer Mode on your system, then proceed to disable and uninstall the Windows Developer Mode.

    If you have enabled the device encryption on your system (BitLocker, VeraCrypt), then proceed and decrypt the drive C: before installing the update.

    Run Windows Update Troubleshooter.


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP

    Wednesday, August 21, 2019 1:52 AM
  • Hi,

     

    Please refer to the reply by S.Sengupta.

     

    Meanwhile, you could Free Up Disk Space with Disk Cleanup.

    https://www.wintips.org/how-to-free-up-disk-space-with-disk-cleanup/

    Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.

     

    Best Regards,

    Farena


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 21, 2019 3:09 AM
  • Hi 
    Thanks for your response.

    i have tried the options you have given still remains same.

    even i have tried to run the setup.exe with below command to avoid the compat scan, but i am not sure whether the command line is correct or not, it was not running on the affected machine.

    can you please give me exact command to run the setup.exe manually to skip the compat issue to get succeed on upgrade.

    Setup.exe /Auto Upgrade /Quiet /Compat IgnoreWarning /CopyLogs C:\Temp\upgrade1903.log


    THANKS SURESH M

    Thursday, August 22, 2019 12:25 PM
  • try this:

    This command works with other switches. For example, to run Setup in the background without any UI:

    Setup /Auto Upgrade /Quiet /Compat ScanOnly

    To ignore common disclaimers in the UI, for example, language changes:

    Setup /Auto Upgrade /Quiet /Compat ScanOnly /Compat IgnoreWarning


    SCCM Admin

    Thursday, August 22, 2019 4:16 PM
  • Thanks for your response.

    even i have tried the command which i posted here to ignore the dismissible compatibility messages and hope that was correct, but not sure why it was not working when i run from the machine which was failed to upgrade to 1903 due to audio driver compatibility issue.

    Please correct me the command line if anything wrong to make a successful run.

    Setup.exe /Auto Upgrade /Quiet /Compat IgnoreWarning /CopyLogs C:\Temp\upgrade1903.log


    THANKS SURESH M

    Friday, August 23, 2019 1:42 PM
  • refer to this site

    https://www.ghacks.net/2018/08/10/windows-10-setup-command-options/

    /Compat {IgnoreWarning / ScanOnly}

    The command defines whether setup should ignore compatibility warnings.


    SCCM Admin

    Friday, August 23, 2019 2:57 PM
  • Hi,

     

    Was your issue solved?

     

    If the reply helped you, please remember to mark it as an answer.

     

    If no, please reply and tell us the current situation in order to provide further help.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 27, 2019 5:52 AM