Powershell problem

Discussion in 'Windows 10' started by urie, Apr 15, 2018.

  1. urie

    urie Moderator Staff Member

    Joined:
    May 21, 2007
    Messages:
    9,035
    Likes Received:
    3,383
    Trophy Points:
    300
    When trying to export windows 10 drivers using powershell using
    Code:
    Export-WindowsDriver -Online -Destination C:\Drivers
    I get How do you want to open this file menu comming up :eek:
    powershell2.png

    Any ideas perhaps file associations.
     
  2. Tiger-1

    Tiger-1 MDL Guru

    Joined:
    Oct 18, 2014
    Messages:
    6,208
    Likes Received:
    7,533
    Trophy Points:
    210
    Hi urie :) well I don't now which OS you are using but anyway you updated it? or still which version of PowerShell that you have so is more easy to help in some manner ok
    Edit. my bad you are using W10 :(
     
  3. l33tissw00t

    l33tissw00t MDL Addicted

    Joined:
    Dec 6, 2012
    Messages:
    818
    Likes Received:
    516
    Trophy Points:
    30
  4. dhjohns

    dhjohns MDL Guru

    Joined:
    Sep 5, 2013
    Messages:
    3,275
    Likes Received:
    1,735
    Trophy Points:
    120
    I use cmd as admin, and dism
    Code:
    dism /online /export-driver /destination:<your drivers folder>
     
  5. BAU

    BAU MDL Addicted

    Joined:
    Feb 10, 2009
    Messages:
    943
    Likes Received:
    2,042
    Trophy Points:
    30
    -LL is most likely broken. But you can view %WINDIR%\Logs\Dism\dism.log
    Several cmdlets can get broken that way, still haven't found a definitive reason. Since I've upgraded to 1803 (mct hack) I can no longer replicate it.
     
  6. urie

    urie Moderator Staff Member

    Joined:
    May 21, 2007
    Messages:
    9,035
    Likes Received:
    3,383
    Trophy Points:
    300
    I tried
    Code:
    Export-WindowsDriver -Online -Destination C:\drivers -LogLevel1
    and
    Code:
    Export-WindowsDriver -Online -Destination C:\drivers -LogLevel3
    should go to default %WINDIR%\Logs\Dism\dism.log no log in there.
     
  7. kaljukass

    kaljukass MDL Guru

    Joined:
    Nov 26, 2012
    Messages:
    2,436
    Likes Received:
    883
    Trophy Points:
    90
    I tested it with Powershell and also with Command Prompt, as You did. Both worked correctly, so I recommend You to check Your system, there must be something incorrect, if You got something else, ie what is shown on attached image.
     
  8. dhjohns

    dhjohns MDL Guru

    Joined:
    Sep 5, 2013
    Messages:
    3,275
    Likes Received:
    1,735
    Trophy Points:
    120
    I just tested with Powershell, and it worked fine.
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\Windows\system32> Export-WindowsDriver -Online -Destination C:\Drivers


    Driver : oem0.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\c7179335.inf_amd64_14671056f7af5d3b\c7179335.inf
    Inbox : False
    ClassName : Display
    BootCritical : False
    ProviderName : Advanced Micro Devices, Inc.
    Date : 1/13/2015 12:00:00 Ante Meridiem
    Version : 8.970.100.9001

    Driver : oem1.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\dlcdcncm.inf_amd64_8acef66ca149ac16\dlcdcncm.inf
    Inbox : False
    ClassName : net
    BootCritical : False
    ProviderName : DisplayLink Corp.
    Date : 4/5/2017 12:00:00 Ante Meridiem
    Version : 8.2.1629.0

    Driver : oem10.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nvvad.inf_amd64_ff7038151d93921b\nvvad.inf
    Inbox : False
    ClassName : MEDIA
    BootCritical : False
    ProviderName : NVIDIA
    Date : 12/13/2017 12:00:00 Ante Meridiem
    Version : 4.4.0.0

    Driver : oem11.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nvvhci.inf_amd64_d673ea7e41b82c50\nvvhci.inf
    Inbox : False
    ClassName : System
    BootCritical : True
    ProviderName : NVIDIA
    Date : 12/27/2016 12:00:00 Ante Meridiem
    Version : 2.2.2151.6378

    Driver : oem14.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\prnms006.inf_amd64_c3bdcb6fc975b614\prnms006.inf
    Inbox : False
    ClassName : Printer
    BootCritical : False
    ProviderName : Microsoft
    Date : 11/29/2016 12:00:00 Ante Meridiem
    Version : 16.0.7629.4000

    Driver : oem17.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\scadrv60.inf_amd64_911acb9fc386ba6a\scadrv60.inf
    Inbox : False
    ClassName : Image
    BootCritical : False
    ProviderName : Hamrick Software
    Date : 8/21/2006 12:00:00 Ante Meridiem
    Version : 1.0.0.49

    Driver : oem18.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\smbusamd.inf_amd64_a1f6e32f30c39b3d\smbusamd.inf
    Inbox : False
    ClassName : System
    BootCritical : True
    ProviderName : Advanced Micro Devices, Inc
    Date : 1/18/2015 12:00:00 Ante Meridiem
    Version : 5.12.0.31

    Driver : oem19.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vclone.inf_amd64_a48dc462de008635\vclone.inf
    Inbox : False
    ClassName : SCSIAdapter
    BootCritical : True
    ProviderName : Elaborate Bytes AG
    Date : 7/24/2013 12:00:00 Ante Meridiem
    Version : 5.4.7.0

    Driver : oem2.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\dlidusb.inf_amd64_95ff6f88bdcd0cf1\dlidusb.inf
    Inbox : False
    ClassName : Display
    BootCritical : False
    ProviderName : DisplayLink
    Date : 5/22/2017 12:00:00 Ante Meridiem
    Version : 8.2.1952.0

    Driver : oem20.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_3b7677a687d61889\prnms009.inf
    Inbox : False
    ClassName : Printer
    BootCritical : False
    ProviderName : Microsoft
    Date : 6/21/2006 12:00:00 Ante Meridiem
    Version : 10.0.17643.1000

    Driver : oem21.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_def1569e3e4379e0\prnms001.inf
    Inbox : False
    ClassName : Printer
    BootCritical : False
    ProviderName : Microsoft
    Date : 6/21/2006 12:00:00 Ante Meridiem
    Version : 10.0.17643.1000

    Driver : oem3.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\dlusbaudio.inf_amd64_2c0851ce609fd24e\dlusbaudio.inf
    Inbox : False
    ClassName : MEDIA
    BootCritical : False
    ProviderName : DisplayLink Corp.
    Date : 4/7/2017 12:00:00 Ante Meridiem
    Version : 8.2.1638.0

    Driver : oem6.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nv_dispi.inf
    Inbox : False
    ClassName : Display
    BootCritical : False
    ProviderName : NVIDIA
    Date : 3/23/2018 12:00:00 Ante Meridiem
    Version : 23.21.13.9135

    Driver : oem7.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nvhda.inf_amd64_cac68a234d08bcc7\nvhda.inf
    Inbox : False
    ClassName : MEDIA
    BootCritical : False
    ProviderName : NVIDIA Corporation
    Date : 12/15/2017 12:00:00 Ante Meridiem
    Version : 1.3.36.6

    Driver : oem8.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nvstusb.inf_amd64_ff404d6aaea214f0\nvstusb.inf
    Inbox : False
    ClassName : USB
    BootCritical : True
    ProviderName : NVIDIA
    Date : 11/28/2017 12:00:00 Ante Meridiem
    Version : 6.14.13.9041

    Driver : oem9.inf
    OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\nvswcfilter.inf_amd64_728b8c2876771de7\nvswcfilter.in
    f
    Inbox : False
    ClassName : Mouse
    BootCritical : True
    ProviderName : NVIDIA
    Date : 7/19/2016 12:00:00 Ante Meridiem
    Version : 8.16.22415.53



    PS C:\Windows\system32>
     
  9. urie

    urie Moderator Staff Member

    Joined:
    May 21, 2007
    Messages:
    9,035
    Likes Received:
    3,383
    Trophy Points:
    300
    That is working :D
     
  10. pisthai

    pisthai Imperfect Human

    Joined:
    Jul 29, 2009
    Messages:
    7,060
    Likes Received:
    2,158
    Trophy Points:
    240
    I'd once that problem to save all drivers at an external location and got it solved to use the work in Safe Mode with Networking from within the Command Prompt (CMD).