So I can confirm that the system reserved partition on this machine was causing the issue as it was very small (14 MB I think). Seems odd because I don't remember seeing that is a requirement anywhere, but maybe I missed it. I used a partition tool to increase it, and that resolved my problem.
Aaron - thank you very much for your help. Greatly appreciated. Dan Franciscus Systems Administrator Information Technology Group Institute for Advanced Study 609-734-8138 From: "Aaron Czechowski" <aaron.czechow...@microsoft.com> To: mdtosd@lists.myitforum.com Sent: Wednesday, September 6, 2017 11:05:24 PM Subject: RE: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Yep, that’s how I’d read that. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Franciscus Sent: Wednesday, 6 September, 2017 18:26 To: mdtosd@lists.myitforum.com Subject: Re: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT So this is the one of the Compat xml files. So if I am reading this correct there is insufficient system partition space? <?xml version="1.0" encoding="utf-8" ?> - <CompatReport xmlns=" [ http://www.microsoft.com/ApplicationExperience/UpgradeAdvisor/01012009 | http://www.microsoft.com/ApplicationExperience/UpgradeAdvisor/01012009 ] "> <System X64Capable="True" X64Running="True" /> <SystemInfo UplevelEdition="Windows 10" OSMajorVersion="6" OSMinorVersion="1" /> - <Hardware> - <HardwareItem HardwareType="Setup_HostIsBootedFromVHD"> <CompatibilityInfo BlockingType="None" /> </HardwareItem> - <HardwareItem HardwareType="Setup_HostIsBootedFromPortableWorkspace"> <CompatibilityInfo BlockingType="None" /> </HardwareItem> - <HardwareItem HardwareType="Setup_HostIsBootedFromAuditMode"> <CompatibilityInfo BlockingType="None" /> </HardwareItem> - <HardwareItem HardwareType="Setup_HostIsUEFICompliant"> <CompatibilityInfo BlockingType="None" /> </HardwareItem> - <HardwareItem HardwareType="Setup_SafeMode"> <CompatibilityInfo BlockingType="None" /> </HardwareItem> - <HardwareItem HardwareType="Setup_HostIsNonStagedBuild"> <CompatibilityInfo BlockingType="None" /> </HardwareItem> - <HardwareItem HardwareType="Setup_InsufficientSystemPartitionDiskSpace" ActualValue1="15"> <CompatibilityInfo BlockingType="Hard" /> <Action Name="Setup_InsufficientSystemPartitionDiskSpace" ResolveState="Hard" /> </HardwareItem> </Hardware> </CompatReport> Dan Franciscus Systems Administrator Information Technology Group Institute for Advanced Study 609-734-8138 From: "Aaron Czechowski" < [ mailto:aaron.czechow...@microsoft.com | aaron.czechow...@microsoft.com ] > To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Sent: Wednesday, September 6, 2017 1:11:38 PM Subject: RE: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT I don’t know if that article gets into it, but you should see a series of XML files in the same directory as setupact.log. open those in notepad or such and look through the list for a hard block. Those often will highlight the issue. Alternatively run setup.exe manually. The setup UI can often pop the specific issue in human readable format. From: [ mailto:listsad...@lists.myitforum.com | listsad...@lists.myitforum.com ] [ [ mailto:listsad...@lists.myitforum.com | mailto:listsad...@lists.myitforum.com ] ] On Behalf Of Daniel Franciscus Sent: Wednesday, 6 September, 2017 07:07 To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Subject: Re: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Thanks Aaron. That is helpful, but still not enough info for me to know what exactly would be causing this. Certainly hardware is not an issue (HP 800 G1) and I have the exact same hardware running Windows 10 already. Would there be a specific log I could look at for this? Dan Franciscus Systems Administrator Information Technology Group Institute for Advanced Study 609-734-8138 From: "Aaron Czechowski" < [ mailto:aaron.czechow...@microsoft.com | aaron.czechow...@microsoft.com ] > To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Sent: Tuesday, September 5, 2017 4:53:34 PM Subject: RE: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Anytime you’re troubleshooting Win10 in-place upgrade, regardless of whether via MDT or SCCM or any other technology, start here: [ https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupgrade%2Fresolve-windows-10-upgrade-errors&data=02%7C01%7Caaron.czechowski%40microsoft.com%7C144e3d827bc74b1cf59d08d4f5315e9b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636403039814360434&sdata=noiumgcie9iYeBvuk19QqeC7YbBsKEcskm2YtAhWbIw%3D&reserved=0 | https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors ] Looks like this is the relevant error code: 0xC1900200 Setup.exe has detected that the machine does not meet the minimum system requirements. Aaron From: [ mailto:listsad...@lists.myitforum.com | listsad...@lists.myitforum.com ] [ [ mailto:listsad...@lists.myitforum.com | mailto:listsad...@lists.myitforum.com ] ] On Behalf Of Jimmy Martin Sent: Tuesday, 5 September, 2017 10:51 To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Subject: RE: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Googled 0xc1800104 [ https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fen.community.dell.com%2Fsupport-forums%2Fsoftware-os%2Ff%2F4997%2Ft%2F19645222&data=02%7C01%7Caaron.czechowski%40microsoft.com%7Ce136848a9e9a476d829b08d4f487950e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636402310537012426&sdata=YvqDNBLTHafBWErLdQW2YEiidWyOsO5iXPDXCEL9GBY%3D&reserved=0 | http://en.community.dell.com/support-forums/software-os/f/4997/t/19645222 ] you upgraded a dell? From: [ mailto:listsad...@lists.myitforum.com | listsad...@lists.myitforum.com ] [ [ mailto:listsad...@lists.myitforum.com | mailto:listsad...@lists.myitforum.com ] ] On Behalf Of Daniel Franciscus Sent: Tuesday, September 5, 2017 12:34 PM To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Subject: Re: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Here is the setuperr.log 2017-09-01 18:25:14, Error MOUPG CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057 2017-09-01 18:27:05, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Suspend(1066): Result = 0xC1800104 2017-09-01 18:27:08, Error MOUPG CSetupManager::ExecuteInstallMode(741): Result = 0xC1900200 2017-09-01 18:27:08, Error MOUPG CSetupManager::ExecuteDownlevelMode(391): Result = 0xC1900200 2017-09-01 18:27:08, Error SP CSetupPlatform::ResurrectNewSystem: Cannot resurrect new system.: Win32Exception: [ file:///C:/$Windows.~BT/Sources/NewSystem.dat | \\?\C:\$Windows.~BT\Sources\NewSystem.dat ] : The system cannot find th e file specified. [0x00000002] __cdecl UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002] 2017-09-01 18:27:14, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104 2017-09-01 18:27:14, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::CheckInitialized(228): Result = 0x80000 00A 2017-09-01 18:27:14, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Cancel(154): Result = 0x8000000A 2017-09-01 18:27:14, Error MOUPG CDlpTask::Cancel(1030): Result = 0x8000000A 2017-09-01 18:27:14, Error MOUPG CDlpManager::Reset(1611): Result = 0x8000000A 2017-09-01 18:27:14, Error MOUPG SetupManager: Reset WinDlp State failed with error [0x8000000A] 2017-09-01 18:27:14, Error MOUPG SetupManager: Failed requested cleanup: [0x8000000A] 2017-09-01 18:27:15, Error MOUPG CSetupManager::Execute(236): Result = 0xC1900200 2017-09-01 18:27:15, Error MOUPG CSetupHost::Execute(372): Result = 0xC1900200 2017-09-01 18:28:15, Error CONX Windows::Compat::Appraiser::SetupAppraiser::StopEtlLogger (2884): Waiting on generaltel process failed: [258].[gle=0x00000102] [WHSS204]: PS C:\windows\Panther\NewOs\Panther> Dan Franciscus Systems Administrator Information Technology Group Institute for Advanced Study 609-734-8138 From: "Jimmy Martin" < [ mailto:jimmy.mar...@bmhcc.org | jimmy.mar...@bmhcc.org ] > To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Sent: Tuesday, September 5, 2017 1:16:52 PM Subject: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Upgrade in place, on the client, you will need to investigate the logs in C:\Windows\Panther Check the setuperr.log Jimmy Martin (901) 227-8209 From: [ mailto:listsad...@lists.myitforum.com | listsad...@lists.myitforum.com ] [ [ mailto:listsad...@lists.myitforum.com | mailto:listsad...@lists.myitforum.com ] ] On Behalf Of Keith Garner Sent: Tuesday, September 5, 2017 11:38 AM To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Subject: [MDT-OSD] RE: Troubleshooting WIndows 10 in-place upgrades from MDT Not enough information here. Can you include the bdd.log and panther logs in a zip file? From: [ mailto:listsad...@lists.myitforum.com | listsad...@lists.myitforum.com ] [ [ mailto:listsad...@lists.myitforum.com | mailto:listsad...@lists.myitforum.com ] ] On Behalf Of Daniel Franciscus Sent: Tuesday, September 5, 2017 8:32 AM To: [ mailto:mdtosd@lists.myitforum.com | mdtosd@lists.myitforum.com ] Subject: [MDT-OSD] Troubleshooting WIndows 10 in-place upgrades from MDT Hi all, I have a machine that is failing to upgrade from Windows 7 to Windows 10 using MDT's task sequence. Below is the results.xml file. I have tried researching some of these errors but it would help if there was a place to look that would provide a specific reason it failed (such as a specific application or driver). Does anyone have an idea of which log file to look at? <Results><Errors>59</Errors><Warnings>14</Warnings><RetVal>-2147467259</RetVal><DeploymentType>UPGRADE</DeploymentType><Messages><![CDATA[Setup failed to upgrade OS from [ file://server/WIN10UPGRADE$/Operati | \\Server\WIN10UPGRADE$\Operati ] ng Systems\Windows 10 Enterprise x64 - 1607\setup.exe, rc = -1047526912 ZTI ERROR - Non-zero return code by LTIApply, rc = 1 Litetouch deployment failed, Return Code = -2147467259 0x80004005 Failed to run the action: Upgrade Windows. Incorrect function. (Error: 00000001; Source: Windows) The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) Failed to run the last action: Upgrade Windows. Execution of task sequence failed. Incorrect function. (Error: 00000001; Source: Windows) Task Sequence Engine failed! Code: enExecutionFail Task sequence execution failed with error code 80004005 SetNamedSecurityInfo() failed. SetObjectOwner() failed. 0x80070005. RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram GetTsRegValue() is unsuccessful. 0x80070002. Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 Failed to run the action: Upgrade Windows. Incorrect function. (Error: 00000001; Source: Windows) The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) Failed to run the last action: Upgrade Windows. Execution of task sequence failed. Dan Franciscus Systems Administrator Information Technology Group Institute for Advanced Study 609-734-8138 This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
