none
Installing NetFX3 failing with Path not found RRS feed

  • Question

  • I have MDT 2013 Update 1 installed with Hyper-V on a Windows 8.1 Enterprise OS. I am trying to install NetFX3 during the State Restore Group in MDT. While NetFx3 is trying to install I get the message:

    FAILURE (5206): The Deployment Wizard was cancelled or did not complete successfully. The deployment will not proceed.
    ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76) Litetouch deployment failed, Return Code = -2147467259 0x80004005

    The ZTIOSRole.log shows:

    Microsoft Deployment Toolkit version: 6.3.8298.1000	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    The task sequencer log is located at C:\Users\admin\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    Roles will be installed.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    No items were specified in variable OSRoles.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    No items were specified in variable OSRoleServices.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    Features specified in Feature:	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
      NetFx3	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
      NetFx4-AdvSrvs	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    No items were specified in variable OptionalOSRoles.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    No items were specified in variable OptionalOSRoleServices.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    No items were specified in variable OptionalOSFeatures.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    ZTI Heartbeat: Processing roles (0% complete	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    Using a local or mapped drive, no connection is required.	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    Copying source files locally from F:\Deploy\Operating Systems\x64\sources\sxs\	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)
    ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)	ZTIOSRole	1/11/2016 8:57:28 AM	0 (0x0000)

    After I click Finish on the Deployment Summary, I see the DVD-ROM drive is not F:, but D:. I did the same setup on my Windows 2012 Server running Hyper-V, but I was able to install NetFx3 just fine without any errors. Anyone know why this is happening and how to fix it? Thanks.




    • Edited by lytvinh Tuesday, January 12, 2016 12:24 PM
    Monday, January 11, 2016 2:33 PM

Answers

  • Ty, I saw that article a while ago and was unable to implement it. I am trying to deploy the OS using an offline media.

    For my Windows 2012 server I only installed MDT 2013 Update 1. When my VM was going through the Task Sequence I noticed while it was on the step "Installing Operating System", the progress was showing ======3.0%=====. This did not happen on my Windows 8.1 computer. Before on my Windows 8.1 computer I had MDT 2013 installed, but not Update 1. After installing Update 1, I opened my existing DeploymentShare with the checkbox "Upgrade the content of the deployment share (if required). But I still could not install NetFx3.


    So just now I uninstalled WADK Windows 10 and MDT 2013 Update 1. Reinstalling both of them and tested, but still was unable to install NetFx3. Looking through the ZTIOSRole.log I could not find the reason why the DEPLOYROOT would be the F: drive. So I checked the ZTIGather.log and saw at the end of the log the WindowsSource variable never gets refreshed and stays at  F:\Deploy\Operating Systems\x64\sources\sxs\ while the %DEPLOYROOT% variable changed from the F: drive to D: after the reboot. I then checked my CustomSettings.ini and BootStrap.ini. I saw that I had my WindowsSource defined in CustomSettings.ini and BootStrap.ini.

    I started investigating why ZTIGather would not redefine the WindowsSource variable. I checked the ZTIGather.xml and saw the line:

    <property id="WindowsSource" type="string" overwrite="false" description="Windows installation files (sxs) needed to install Windows 8 features that are not in the image" />

    I tried changed the overwrite to "true", but still couldn't get it to go, so I changed the value back. I checked that WindowsSource was showing in CustomSettings.ini and Bootstrap.ini for both my DeploymentShare and my Media rules. Putting a WindowsSource task sequence variable in the task sequence didn't work either. So I deleted all the entries regarding WindowsSource. Then I started only putting WindowsSource=%DEPLOYROOT%Operating Systems\x64\sources\sxs\ in my CustomSettings.ini and Bootstrap for my DeploymentShare and my Media rules one by one. After extension testing I have concluded that you can ONLY have WindowsSource variable in the Bootstrap.ini for your DeploymentShare. If you have additional entries anywhere, it will break.

    I am curious as to why that is though. If anyone can answer that question, that would be appreciated. Thanks.


    • Marked as answer by lytvinh Wednesday, January 13, 2016 2:29 PM
    • Edited by lytvinh Wednesday, February 24, 2016 6:19 PM
    Wednesday, January 13, 2016 2:29 PM
  • So it seems like my resolution is not the resolution. I found out if you complete a task sequence and then run one after it, installing NetFx3 will fail unless you do a clean before starting the second one. If you add WindowsSource in the CS.ini or Bootstrap.ini from the Deployment Share folder, you'll get the message "ERROR - NetFx3 role Processing with DISM.exe fialed, rc = -2146498298". If you add WindowsSource in the CS.ini or Bootstrap.ini in your offline media, then you'll get the message:

    ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)
    Litetouch deployment failed, Return Code = -2147467259I

    This is definitely a bug. I just upgraded to MDT 2013 Update 2 and thought it might fix it, but doesn't.

    • Marked as answer by lytvinh Wednesday, February 24, 2016 8:15 PM
    Wednesday, February 24, 2016 8:15 PM

All replies

  • This will solve your issue with NetFX3 http://blogs.technet.com/b/deploymentguys/archive/2012/11/13/windows-8-automating-the-installation-of-net-framework-3-5-with-mdt.aspx

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    • Marked as answer by Ty GlanderModerator Wednesday, January 13, 2016 2:55 AM
    • Unmarked as answer by lytvinh Wednesday, January 13, 2016 2:29 PM
    Wednesday, January 13, 2016 2:55 AM
    Moderator
  • Ty, I saw that article a while ago and was unable to implement it. I am trying to deploy the OS using an offline media.

    For my Windows 2012 server I only installed MDT 2013 Update 1. When my VM was going through the Task Sequence I noticed while it was on the step "Installing Operating System", the progress was showing ======3.0%=====. This did not happen on my Windows 8.1 computer. Before on my Windows 8.1 computer I had MDT 2013 installed, but not Update 1. After installing Update 1, I opened my existing DeploymentShare with the checkbox "Upgrade the content of the deployment share (if required). But I still could not install NetFx3.


    So just now I uninstalled WADK Windows 10 and MDT 2013 Update 1. Reinstalling both of them and tested, but still was unable to install NetFx3. Looking through the ZTIOSRole.log I could not find the reason why the DEPLOYROOT would be the F: drive. So I checked the ZTIGather.log and saw at the end of the log the WindowsSource variable never gets refreshed and stays at  F:\Deploy\Operating Systems\x64\sources\sxs\ while the %DEPLOYROOT% variable changed from the F: drive to D: after the reboot. I then checked my CustomSettings.ini and BootStrap.ini. I saw that I had my WindowsSource defined in CustomSettings.ini and BootStrap.ini.

    I started investigating why ZTIGather would not redefine the WindowsSource variable. I checked the ZTIGather.xml and saw the line:

    <property id="WindowsSource" type="string" overwrite="false" description="Windows installation files (sxs) needed to install Windows 8 features that are not in the image" />

    I tried changed the overwrite to "true", but still couldn't get it to go, so I changed the value back. I checked that WindowsSource was showing in CustomSettings.ini and Bootstrap.ini for both my DeploymentShare and my Media rules. Putting a WindowsSource task sequence variable in the task sequence didn't work either. So I deleted all the entries regarding WindowsSource. Then I started only putting WindowsSource=%DEPLOYROOT%Operating Systems\x64\sources\sxs\ in my CustomSettings.ini and Bootstrap for my DeploymentShare and my Media rules one by one. After extension testing I have concluded that you can ONLY have WindowsSource variable in the Bootstrap.ini for your DeploymentShare. If you have additional entries anywhere, it will break.

    I am curious as to why that is though. If anyone can answer that question, that would be appreciated. Thanks.


    • Marked as answer by lytvinh Wednesday, January 13, 2016 2:29 PM
    • Edited by lytvinh Wednesday, February 24, 2016 6:19 PM
    Wednesday, January 13, 2016 2:29 PM
  • That is strange.

    Can you post BDD.log to something like OneDrive and share the link here?


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.



    Wednesday, January 13, 2016 8:27 PM
    Moderator
  • You only have to configure your Deployment Share and import your operating system not as a custom image file, but as a full set of source files, which are the ones that are located on your original installation media, for example. If you have a custom wim file, I think that you may replace the original "install.wim" with your one.


    • Edited by DashKappei Wednesday, January 13, 2016 8:33 PM
    Wednesday, January 13, 2016 8:32 PM
  • So it seems like my resolution is not the resolution. I found out if you complete a task sequence and then run one after it, installing NetFx3 will fail unless you do a clean before starting the second one. If you add WindowsSource in the CS.ini or Bootstrap.ini from the Deployment Share folder, you'll get the message "ERROR - NetFx3 role Processing with DISM.exe fialed, rc = -2146498298". If you add WindowsSource in the CS.ini or Bootstrap.ini in your offline media, then you'll get the message:

    ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)
    Litetouch deployment failed, Return Code = -2147467259I

    This is definitely a bug. I just upgraded to MDT 2013 Update 2 and thought it might fix it, but doesn't.

    • Marked as answer by lytvinh Wednesday, February 24, 2016 8:15 PM
    Wednesday, February 24, 2016 8:15 PM