Windows 10: Win 10 RS-4 not compatible with Intel DX58SO motherboard Solved

Page 12 of 25 FirstFirst ... 2101112131422 ... LastLast
  1.    18 Dec 2017 #111

    Still getting the same error with both of them
    ---------------------------------------------------
    PS C:\Windows\system32> dism /image:mount /add-driver /Driver:"c:\drivers" /recurse
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    Error: 2
    Unable to access the image.
    Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.
    ------------------------------------------------------------
    I can’t access that link getting “404 Error - Sorry this document can't be found.” https://docs.microsoft.com/en-us/pre...25070(v=win.10)
    So I’m having a look here:
    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825070(v=win.10)


    Not that I understand anything from that site

    I’m trying:)




    Attached Thumbnails Attached Thumbnails dism.jpg  
      My ComputerSystem Spec

  2.    18 Dec 2017 #112

    What have I done, did it do it and did it go to the right place?

    dism /image:c:\mount /add-driver /Driver:"c:\drivers" /recurse
    Attached Thumbnails Attached Thumbnails dism.jpg  
      My ComputerSystem Spec

  3.    18 Dec 2017 #113

    I think it was ok what do you think?
    -------------------------------------------------------
    PS C:\Windows\system32> dism /image:c:\mount /add-driver /Driver:"c:\drivers" /recurse

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.17025.1000

    Searching for driver packages to install...
    Found 8 driver package(s) to install.
    Installing 1 of 8 - c:\drivers\bcmwlhigh63.inf_amd64_c17d38c267d5edb2\bcmwlhigh63.inf: The driver package was successfully installed.
    Installing 2 of 8 - c:\drivers\e_gf1lee.inf_amd64_57076ef5e48eb106\E_GF1LEE.INF: The driver package was successfully installed.
    Installing 3 of 8 - c:\drivers\ese9.inf_amd64_598dfe54fdbe05e8\ese9.inf: The driver package was successfully installed.
    Installing 4 of 8 - c:\drivers\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nv_ref_pubwu.inf: The driver package was successfully installed.
    Installing 5 of 8 - c:\drivers\nvhda.inf_amd64_fd09272cf916c617\nvhda.inf: The driver package was successfully installed.
    Installing 6 of 8 - c:\drivers\nvstusb.inf_amd64_13f03faeef8601fe\nvstusb.inf: The driver package was successfully installed.
    Installing 7 of 8 - c:\drivers\prnms001.inf_amd64_db986f156726d3d7\prnms001.Inf: The driver package was successfully installed.
    Installing 8 of 8 - c:\drivers\prnms009.inf_amd64_5812eb3d390ac060\prnms009.Inf: The driver package was successfully installed.
    The operation completed successfully.
    PS C:\Windows\system32>
    ----------------------------------------
      My ComputerSystem Spec

  4.    18 Dec 2017 #114

    Must have worked D:\mount is with no added drivers and C:\mount is with the added drivers
    Attached Thumbnails Attached Thumbnails worked.jpg  
      My ComputerSystem Spec


  5. Posts : 1,927
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #115

    Just returned from park with Dog.

    Looks promising :)
      My ComputersSystem Spec

  6.    18 Dec 2017 #116

    That was just a lucky shot:)

    Now how to work out the rest of the commands

    "dism /unmount-wim /mountdir:mount /commit" comes up with an error 50

    Any ideas with the rest of the commands please?
    --------------------------------------------------------------
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\Windows\system32> dism /unmount-wim /mountdir:mount /commit

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Error: 50

    The request is not supported.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    PS C:\Windows\system32>
    -------------------------------------------------------
      My ComputerSystem Spec


  7. Posts : 1,927
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #117

    dism /unmount-wim /mountdir:mount /commit

    Since you are using c:\mount, try replace with:

    dism /unmount-wim /mountdir:C:\mount /commit
      My ComputersSystem Spec

  8.    18 Dec 2017 #118

    Fafhrd said: View Post
    dism /unmount-wim /mountdir:mount /commit

    Since you are using c:\mount, try replace with:

    dism /unmount-wim /mountdir:C:\mount /commit
    Tried that already and lost all the files from C:\mount , it’s now completely empty:)


    dism /unmount-wim /MountDir:c:\mount /commit
    Any ideas?
    ---------------------------------------------------------------------
    PS C:\Windows\system32> dism /unmount-wim /MountDir:c:\mount /commit

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image File : c:\iso\sources\boot.wim
    Image Index : 2
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]

    Error: 0xc1420117

    The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    PS C:\Windows\system32>
    --------------------------------------------------------------------
      My ComputerSystem Spec


  9. Posts : 1,927
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #119

    When you unmount the Wim, the Mount folder empties as the changes are committed to the wim file.

    If there's no error message, the command has completed successfully.

    You can use 7-zip file manager to peek into wim files.

    or you can mount the wim files again to search with file explorer for the driver files you have saved in c:\drivers.

    If you get an error message like that close all explorer windows, etc., that may be using the c:\mount folder.

    I've revisited the earlier post #107 I made:

    Fafhrd said: View Post
    I think you need to export drivers using Powershell (Admin) from your working windows installation, with the command
    Fafhrd said: View Post
    Export-WindowsDriver -Online -Destination D:\Drivers
    where D:\drivers is a folder you have made on a destination D: drive (your choice of destination)
    Create a D:\iso folder
    Create a d:\mount folder, then you need to open (mount to a virtual DVD) your chosen ISO e.g. from Download Windows 10 Insider Preview Advanced and copy the contents to D:\iso. I would not use an ISO created from UUP files from the 170xx series of builds.

    Then mount the boot.wim with DISM
    dism /mount-wim /wimfile:d:\iso\sources\boot.wim /index:2 /mountdir:d:\mount
    then
    dism /image:D:\mount /add-driver /Driver:d:\drivers /recurse
    then
    dism /unmount-wim /mountdir:D:\mount /commit

    then repeat with install.wim

    first check the index:

    dism /Get-WimInfo /WimFile:d:\iso\sources\install.wim

    Then if the required image is 1

    dism /mount-wim /wimfile:d:\iso\sources\install.wim /index:1 /mountdir:d:\mount
    then
    dism /image:D:\mount /add-driver /Driver:d:\drivers /recurse
    then
    dism /unmount-wim /mountdir:d:\mount /commit

    Now the contents of D:\ISO have had the drivers from 16299 added to the boot and install WIMfiles. None of the 170xx drivers have been removed.

    In theory you can now create a USB setup drive or a DVD or just install from the setup files in the ISO folder.

    Will this work for you? I don't know! I'm sure if there are deficiencies or improvements to be made, someone will step in to point them out.

    Edit: Modifications and added text in RED
    the dism commands do not need powershell, they will run from an admin cmd prompt.
      My ComputersSystem Spec

  10.    18 Dec 2017 #120

    So should I do what the error suggests and then continue to the next step?

    ---------------------------------------
    Error: 0xc1420117

    The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process.
    -------------------------------------------------------------------------



    Edit:

    Just seen your modifications, thank you:)
      My ComputerSystem Spec


 
Page 12 of 25 FirstFirst ... 2101112131422 ... LastLast

Related Threads
Read more: Intel: We're ending all legacy BIOS support by 2020 | ZDNet See also: http://www.uefi.org/sites/default/files/resources/Brian_Richardson_Intel_Final.pdf
I spoke to Microsoft after they re-installed latest windows 10. There were some buggy issues after the update, e.g couldnt click windows icon at bottom left corner, black screen with white mouse on loading my account from startup (this happend...
Solved Intel Motherboard Powerup in Drivers and Hardware
Just bought a used Intel DQ57TM motherboard with i5-650 CPU. As I am going away on hols tomorrow, I quickly connected it up to a good power supply plus internal speaker, resting the mobo on an insulated surface. No other connections were made. ...
Intel DX58SO MB & Win 10 in Installation and Upgrade
Has anyone upgraded their Intel DX58SO system to Win 10? If so, are there any issues? Intel hasn't, and likely won't, update the 5 Series drivers for the new OS. The latest available on the Intel Download Center are Win 7 drivers. I'm...
Solved Intel DX58SO compatibility with XEON in PC Custom Builds and Overclocking
I'd like to ask if someone has a XEON running on that mobo. I would like to buy one and would like to make sure that it runs on this mobo. I'm using the latest BIOS, SOX5810J.86.5600 dated 07/29/2013. Thanks for all advice in advance!
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 05:49.
Find Us