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

Page 14 of 25 FirstFirst ... 4121314151624 ... LastLast
  1. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #131

    You could follow what I'm doing.
    I'm just going through the process myself on an old laptop - I Created the 3 folders:
    Click image for larger version. 

Name:	image.png 
Views:	11 
Size:	12.8 KB 
ID:	1686790 %x
    Exported the drivers:

    Code:
    Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved.C:\windows\system32>powershellWindows PowerShellCopyright (C) 2016 Microsoft Corporation. All rights reserved.PS C:\windows\system32> Export-WindowsDriver -Online -Destination c:\DriversDriver           : oem0.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_x86_1fd2a6680e86dac8\prnms009.infInbox            : FalseClassName        : PrinterBootCritical     : FalseProviderName     : MicrosoftDate             : 6/21/2006 12:00:00 AMVersion          : 10.0.14393.0Driver           : oem1.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_x86_926cf268815ef31e\prnms001.infInbox            : FalseClassName        : PrinterBootCritical     : FalseProviderName     : MicrosoftDate             : 6/21/2006 12:00:00 AMVersion          : 10.0.14393.0Driver           : oem10.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\ich8ahci.inf_x86_8018ff02956cd757\ich8ahci.infInbox            : FalseClassName        : hdcBootCritical     : TrueProviderName     : IntelDate             : 12/6/2006 12:00:00 AMVersion          : 6.8.0.3002Driver           : oem11.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\wn111.inf_x86_2ed67859bc8e7c0b\wn111.infInbox            : FalseClassName        : NetBootCritical     : FalseProviderName     : NetgearDate             : 10/26/2007 12:00:00 AMVersion          : 1.0.4.3Driver           : oem12.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\ianvstor.inf_x86_e266caf6640511e8\ianvstor.infInbox            : FalseClassName        : SCSIAdapterBootCritical     : TrueProviderName     : IntelDate             : 2/2/2009 12:00:00 AMVersion          : 1.9.0.1006Driver           : oem13.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\oemwin2k.inf_x86_d4d9d46016f5c5b1\oemwin2k.infInbox            : FalseClassName        : NetBootCritical     : FalseProviderName     : TAP-Win32 Provider V9Date             : 9/13/2006 12:00:00 AMVersion          : 16.0.0.4Driver           : oem14.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\sndtaudio.inf_x86_bc6dea744054abbb\sndtaudio.infInbox            : FalseClassName        : MEDIABootCritical     : FalseProviderName     : SndTAudioDate             : 4/4/2008 12:00:00 AMVersion          : 6.1.10102.333Driver           : oem15.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\w9xel90x.inf_x86_22466be5485ccc68\w9xel90x.infInbox            : FalseClassName        : NetBootCritical     : FalseProviderName     : 3ComDate             : 8/2/2001 12:00:00 AMVersion          : 4.6.1.0Driver           : oem16.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nvmpu.inf_x86_d9c4878640c967ad\nvmpu.infInbox            : FalseClassName        : MediaBootCritical     : FalseProviderName     : NVIDIA CorporationDate             : 1/26/2005 12:00:00 AMVersion          : 6.14.460.0Driver           : oem17.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\965m.inf_x86_f7bebb7e493ba4a0\965m.infInbox            : FalseClassName        : SystemBootCritical     : TrueProviderName     : IntelDate             : 9/15/2006 12:00:00 AMVersion          : 8.2.0.1000Driver           : oem18.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\w29n51.inf_x86_d7359a4d02a600d6\w29n51.infInbox            : FalseClassName        : netBootCritical     : FalseProviderName     : IntelDate             : 7/25/2007 12:00:00 AMVersion          : 9.0.4.37Driver           : oem19.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\alcxau22.inf_x86_da22471eb9d3f6ec\alcxau22.infInbox            : FalseClassName        : MEDIABootCritical     : FalseProviderName     : Realtek Semiconductor Corp.Date             : 6/19/2009 12:00:00 AMVersion          : 6.0.1.6305Driver           : oem2.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\915m.inf_x86_52df64ae28e7d21d\915m.infInbox            : FalseClassName        : SystemBootCritical     : TrueProviderName     : IntelDate             : 5/26/2004 12:00:00 AMVersion          : 6.1.0.1008Driver           : oem20.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\wdma_int.inf_x86_6943113be78c78cd\wdma_int.infInbox            : FalseClassName        : MEDIABootCritical     : FalseProviderName     : MicrosoftDate             : 7/29/2008 12:00:00 AMVersion          : 6.0.6001.18000Driver           : oem21.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\rt2500.inf_x86_1deeb4cebc1784f9\rt2500.infInbox            : FalseClassName        : NetBootCritical     : FalseProviderName     : LinksysDate             : 4/21/2005 12:00:00 AMVersion          : 3.0.3.0Driver           : oem22.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\mcdbus.inf_x86_6595927e3db13b6a\mcdbus.infInbox            : FalseClassName        : SCSIAdapterBootCritical     : TrueProviderName     : MagicISO, Inc.Date             : 2/24/2009 12:00:00 AMVersion          : 2.7.106.0Driver           : oem23.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\synpd.inf_x86_82000f1307639094\synpd.infInbox            : FalseClassName        : MouseBootCritical     : TrueProviderName     : SynapticsDate             : 8/5/2015 12:00:00 AMVersion          : 19.0.19.1Driver           : oem3.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\wlphonecv.inf_x86_2cf7d8328abf0baa\wlphonecv.infInbox            : FalseClassName        : USBBootCritical     : TrueProviderName     : MSNDate             : 2/14/2007 12:00:00 AMVersion          : 1.2.0.7Driver           : oem4.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\yk62x86.inf_x86_98dcbf29bdd291e8\yk62x86.infInbox            : FalseClassName        : NetBootCritical     : FalseProviderName     : MarvellDate             : 8/6/2009 12:00:00 AMVersion          : 11.10.10.3Driver           : oem5.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\oem2.inf_x86_a01f7eed6cb90306\oem2.infInbox            : FalseClassName        : MonitorBootCritical     : FalseProviderName     : LGDate             : 10/15/2007 12:00:00 AMVersion          : 1.0.0.0Driver           : oem6.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\oem0.inf_x86_aaa3fadd9b824419\oem0.infInbox            : FalseClassName        : MEDIABootCritical     : FalseProviderName     : VIA Technologies, Inc.Date             : 10/3/2006 12:00:00 AMVersion          : 6.14.1.4180Driver           : oem7.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\atk2000.inf_x86_b17c6a10719e3b19\atk2000.infInbox            : FalseClassName        : SystemBootCritical     : TrueProviderName     : ATKDate             : 8/13/2004 12:00:00 AMVersion          : 1043.2.15.37Driver           : oem8.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\belkin.inf_x86_2025b6af8627582d\belkin.infInbox            : FalseClassName        : NetBootCritical     : FalseProviderName     : Belkin CorporationDate             : 3/12/2007 12:00:00 AMVersion          : 6.1099.312.2007Driver           : oem9.infOriginalFileName : C:\Windows\System32\DriverStore\FileRepository\fasttx2k.inf_x86_5dc060c63b45ae92\fasttx2k.infInbox            : FalseClassName        : SCSIAdapterBootCritical     : TrueProviderName     : Promise TechnologyDate             : 6/9/2003 12:00:00 AMVersion          : 1.0.1.29PS C:\windows\system32>
    I've downloaded the ISO, and mounted it, and copied the contents to c:\iso

    Click image for larger version. 

Name:	image.png 
Views:	5 
Size:	268.1 KB 
ID:	168680
    I'll break off for it to finish.
      My ComputersSystem Spec

  2. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #132

    I can see that I will run out of space on that drive, I need to make a few adjustments...
      My ComputersSystem Spec

  3.    18 Dec 2017 #133

    Ok deleted everything, starting fresh by following you

    Don’t lead us over a cliff edge will you:)
      My ComputerSystem Spec

  4. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #134

    I had to create a new partition , J: to hold the ISO and Mount folder - all your folders are on C: - c:\ISO, c:\Drivers and C:\Mount

    I'll try not to throw you off the Mount...

    Here we go:

    Click image for larger version. 

Name:	image.png 
Views:	3 
Size:	342.1 KB 
ID:	168685

    just finished copying the ISO to J:\iso
      My ComputersSystem Spec

  5. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #135

    Right, I've modified the Dism cmdlets for my J: drive (all yours are C:)

    dism /mount-wim /wimfile:j:\iso\sources\boot.wim /index:2 /mountdir:j:\mount

    then
    dism /image:j:\mount /add-driver /Driver:c:\drivers /recurse
    then
    dism /unmount-wim /mountdir:j:\mount /commit


    then repeat with install.wim


    first check the index:


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


    Then if the required image is 8


    dism /mount-wim /wimfile:j:\iso\sources\install.wim /index:8 /mountdir:j:\mount
    then
    dism /image:j:\mount /add-driver /Driver:c:\drivers /recurse
    then
    dism /unmount-wim /mountdir:j:\mount /commit

    first cmdlet done:
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	19.5 KB 
ID:	168688

    lets see boot.wim mounted:

    Click image for larger version. 

Name:	image.png 
Views:	3 
Size:	74.6 KB 
ID:	168689
    Click image for larger version. 

Name:	image.png 
Views:	10 
Size:	17.3 KB 
ID:	168690
    ok, 1.33 GB

    second cmdlet

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	99.5 KB 
ID:	168692
    success!
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	140.1 KB 
ID:	168693
    OK 1.61GB with drivers installed in boot.wim, lets see where they are:
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	67.1 KB 
ID:	168694

    yep, in the Driverstore\FileRepository as I guessed.
    close down all file explorer windows for j:\mount etc.
    third cmdlet taking its time... done

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	123.2 KB 
ID:	168695
    Boot.wim modified
      My ComputersSystem Spec

  6. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #136

    checking the install.wim image:

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	80.8 KB 
ID:	168698

    Image 8 for Pro. I expect things may take longer for this image, but so far seems ok for mounting install.wim

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	119.4 KB 
ID:	168700
    ok 7.74 GB
    cmdlet 2, add drivers
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	166.8 KB 
ID:	168701
    8.02 GB, close explorer windows for unmounting with final cmdlet, taking its time...but on the basis of the boot.wim progress, it should pick up pace...unmounting now...
    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	145.7 KB 
ID:	168702
    all done.

    One thing about these old drivers - they may be unsigned. I may need to modify this cmdlet to allow unsigned drivers - on the other hand, that may just be for x64 drivers.

    dism /image:j:\mount /add-driver /Driver:c:\drivers /recurse

    Well Bordi, how have you got on?
      My ComputersSystem Spec

  7.    18 Dec 2017 #137

    Having problems copying the contents of the mounted ISO into the iso file
    I keep getting the error
    The specified image in the specified wim is already mounted for read/write access.
    -----------------------------------------------------
    C:\Windows\system32>dism /mount-wim /wimfile:c:\iso\sources\boot.wim /index:2 /mountdir:c:\mount
    Error: 0xc1420127
    The specified image in the specified wim is already mounted for read/write access.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    C:\Windows\system32>
    ----------------------------------------------------
    How did you copy the contents just copy and paste or did you use a command?

    It worked before; I don’t see why it’s not working now
      My ComputerSystem Spec

  8.    18 Dec 2017 #138

    I deleted the iso file just in case there were hidden files in there
    Coppied over the mounted ISO file several times but still when I use the command

    “dism /mount-wim /wimfile:c:\iso\sources\boot.wim /index:2 /mountdir:c:\mount”

    I get the same error

    The specified image in the specified wim is already mounted for read/write access.
    Attached Thumbnails Attached Thumbnails cmd.jpg  
      My ComputerSystem Spec

  9. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       18 Dec 2017 #139

    it's pointing you to the dism log for information.
    try the unmount cmdlet

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

  10.    18 Dec 2017 #140

    Fafhrd said: View Post
    it's pointing you to the dism log for information.
    try the unmount cmdlet

    dism /unmount-wim /mountdir:c:\mount /commit
    Microsoft Windows [Version 10.0.16299.125]
    (c) 2017 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>dism /unmount-wim /mountdir:c:\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

    C:\Windows\system32>
      My ComputerSystem Spec


 
Page 14 of 25 FirstFirst ... 4121314151624 ... 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 15:21.
Find Us