1.14 Driver package

I'm not sure I should do this - but for the desperate ones amongst us an offering from Leadtek - CAUTION may not work for MSI
Audio driver 2.99 (WHQL'd)
Audio utilities 3.01
Network driver 2.81 (WHQL'd)
GART driver 2.78 (WHQL'd)
SMBus driver 2.75 (WHQL'd)
Memory controller driver 2.75 (WHQL'd)
IDE driver 2.70 In The Box (WHQL'd)
IDE driver 2.96 Full Driver
Installer 3.01
FTP download only
http://ftp://ftp.leadtek.com.tw/mb/K7NCR18X/A1.14/WinFast_K7NCR18X_W2KXPdrv.zip
As always at your own risk  :(

at least they're getting close :D
Maybe it'll be the 1.15 driver package that works....

Similar Messages

  • HP LaserJet Pro 300/400 (M375nw & M475dn) - Driver packages will not install

    Hello all,
    I need some assistance with a very persistent and frustrating issue trying to get driver software packages for our LaserJet M375nw & M475dn to install correctly. We are running Windows 7 Pro x64 on HP 8300 desktop PCs.
    We have these printers printing properly via our print server and the proper .inf driver but need the ability to scan to the PC. I would like to install the HP-provided software packages (which include the Scan driver & utility) but am running into the error below.
    "A problem occurred while preparing to install software to your system. Please restart your computer, and run this installer again. If the problem persists, please check the product support web site for your product."
    I get this error at 80% in the "preparing to install" process. I am using the latest drivers from the website for each of these models (which actually use the same package). I have tried both the Full and Basic driver package with the same results.
    We have these printers installed via a static IP on the Network, not USB. I am trying to install as a Local Administrator. UAC is disabled. The PC is fully updated and doesn't have much in the way of custom software. It has SCCM client, MS SQL Native Client, Google Earth, Adobe, Trend Micro AV, OnBase, Office 2007 and Chrome installed.
    Here are some of the things I've tried w/o success:
    Tried installing with latest drivers from HP website
    Ran all Windows updates
    Ran the Scrubber uninstaller provided in the package / Running "uninstall" executable from HP software
    Disabled all non-MS startup programs/services in msconfig, disabled Antivirus, rebooted, tried to again
    Restarting computer (many, many times between different troubleshooting steps)
    Tried disabling "Smart Install" (though I think this only applies to USB connections)
    Checked print spooler - it indeed is started/running properly
    Uninstalled all HP-branded software
    Can any of you offer some help please? I'm not sure what to try next.
    Some other posts I've looked at w/ no success are:
    http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-Setup/HP-CM1410-Series-install-error/td-p/3960480/page/2
    http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c02018709
    http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?sp4ts.oid=4208157&spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c03123997-9%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken
    http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-Setup/laserjet-pro-200-error/td-p/2702269
    http://h30434.www3.hp.com/t5/Printer-All-in-One-Software-Drivers/laserjet-pro-400-color-MFP-m475dw-scanner-stopped-working-in/td-p/3109875
    Thank you!!!
    P.S. This thread has been moved from Laserjet to Multifunction and All-in-One. - Hp Forum moderator
     

    This is soulsecur again. I have used the FileToEmail.exe Utlity in the Driver package to generate logs. I looked through the installer log (hpbcsiInstaller.log) and found the info below. Can someone please help me make sense of this error? 08:49:12.7343 Information DriverPDUEngine.DriverPackagePreInstall(): Entry. 08:49:12.7343 Information DriverPDUEngine.DriverPackagePreInstall(): Preload Driver INF file list count = 1
    08:49:12.7343 Information DriverPDUEngine.DriverPackagePreInstall(): INF File: ..\\hppasc19.inf
    08:49:12.7343 Information DriverPDUEngine.DriverPackagePreInstall(): Tested infFile. name: ..\\hppasc19.inf
    08:49:12.7343 Information DriverPDUEngine.DriverPackagePreInstall(): Tested infFile. m_installDriverInfFileName: ..\\hppasc19.inf
    08:49:12.7343 Information DriverPDUEngine.DriverPackagePreInstall(): Tested infFile. isPrinterDriver: True
    08:49:12.7343 Information DifxHandler.DriverPackagePreInstall(): Entry.
    08:49:12.7343 Information DifxHandler.DriverPackagePreInstall(): Calling DIFxServiceClient.DriverPackagePreInstall(): file = ..\\hppasc19.inf
    08:49:12.7343 Information DifxHandler.DriverPackagePreInstall(): Calling DIFxDriverPackagePreInstall(): file = ..\\hppasc19.inf
    08:49:12.7343 Information DIFxServiceClient.WaitForInitialCreateChannel(): Checking to see if the Channel has been created.
    08:49:12.7343 Information DIFxServiceClient.CheckStatus(): Checking status of Service
    08:49:13.0643 Information DIFxServiceClient.FixChannel(): Channel appears to be ok
    08:49:13.1424 !ERROR! DIFxServiceClient.DIFxDriverPackagePreInstall(): Caught Fault Exception
    08:49:13.1424 !ERROR! DIFxServiceClient.DIFxDriverPackagePreInstall(): Exception Detail Message: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
    08:49:13.1424 !ERROR! DIFxServiceClient.DIFxDriverPackagePreInstall(): Exception Message: DIFxService:IFxServiceDriverPackagePreInstall Logs:08:49:13.06 ServiceMarshaller PreInstalling inf: ..\\hppasc19.inf
    08:49:13.06 ServiceMarshaller Calling DIFxAPI.DriverPackagePreInstall. INF File: ..\\hppasc19.inf, Flags = 2
    08:49:13.1424 !ERROR! DIFxServiceClient.DIFxDriverPackagePreInstall(): DIFxService:IFxServiceDriverPackagePreInstall Logs:08:49:13.06 ServiceMarshaller PreInstalling inf: ..\\hppasc19.inf
    08:49:13.06 ServiceMarshaller Calling DIFxAPI.DriverPackagePreInstall. INF File: ..\\hppasc19.inf, Flags = 2
    08:49:13.1424 Exception
    System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] DIFxService:IFxServiceDriverPackagePreInstall Logs:08:49:13.06 ServiceMarshaller PreInstalling inf: ..\\hppasc19.inf
    08:49:13.06 ServiceMarshaller Calling DIFxAPI.DriverPackagePreInstall. INF File: ..\\hppasc19.inf, Flags = 2 Void HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)
    Server stack trace:
    at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at HP.InstallManager.CSI.IDIFxServiceMarshaller.DIFxServiceDriverPackagePreInstall(String infName)
    at HP.InstallManager.CSI.DIFxServiceClient.DIFxDriverPackagePreInstall(String infName)
    DifxHandler.DriverPackagePreInstall => DIFxServiceClient.DIFxDriverPackagePreInstall => NLogLogger.HP.CommonTools.CSI.ILogger.LogError
    08:49:13.2024 Information DIFxServiceClient.DIFxDriverPackagePreInstall(): proxy State: Opened
    08:49:13.2024 Information DifxHandler.DriverPackagePreInstall(): DIFxDriverPackagePreInstall(): returned: -1
    08:49:13.2024 !ERROR! DifxHandler.DriverPackagePreInstall(): DIFxServiceClient Preinstall failed: code = -1
    08:49:13.2024 !ERROR! DifxHandler.DriverPackagePreInstall(): DIFxServiceClient Preinstall failed: Error string = Unknown error (0xffffffff)
    08:49:13.2024 Information DifxHandler.DriverPackagePreInstall(): Returning: FinishedFailError
    08:49:13.2024 Information DriverPDUEngine.DriverPackagePreInstall(): Returning FinishedFailError
    08:49:13.2024 Information DriverPDUEngine.HandleDIFXAction(): Returning: FinishedFailError
    08:49:13.2024 Information InstallManager.FireStatusEvent(): Firing Status event. Sender = Driver PDU Engine, Text = HP.InstallConfig.CSI.PDUEngineActionItem, Status = FinishedFailError
    08:49:13.2024 Information PDUManager.get_PrepareToInstallPercentComplete(): m_stepCountPrepareToInstall = 26, m_numStepsPrepareToInstall = 32
    08:49:13.2024 Information InstallManager.get_PrepareToInstallPercentComplete(): Prepare to install percent complete = 81
    08:49:13.2024 Verbose CSIViewModel.PagePropertyChangedHandler(): >>>>>>> Property Raised - CurrentPercentage
    08:49:13.2024 Verbose CSIPageViewModelBase.CheckForUserError(): Checking for User Error: - EventStatus: FinishedFailError

  • How to Add Multiple Driver Packages Using Reference File via PowerShell

    Hey All - 
    I've got a task I'm working on which would be much easier via PowerShell.  I tried figuring it out, but couldn't so thought I'd post.
    The Task
    I need to create about 50 new, empty driver packages (most are in the same folder in the console) and am trying to find a method of doing so where I may use a source text file / csv file as reference in the command line.  Each package has a unique name
    and source path.  Here are examples:
    - Latitude E5440 Win7 x86 [A01]   \\server\drivers\5440x86
    - Latitude E5440 Win7 x64 [A01]   \\server\drivers\5440x64
    The Structure
    All of the ones I want to add via PowerShell will go into the same folder in the console.  They will be in the folder "root\New Drivers\Dell CAB Drivers" 
    Any ideas or will this just take more time than it's worth for 50?  Thanks!
    Ben K.

    Also, the creation of the driver package won't be your biggest challenge, as it's as simple as New-CMDriverPackage (see:
    http://technet.microsoft.com/en-us/library/jj821724(v=sc.20).aspx).
    The biggest challenge is relating your models to a share name (unless they're all Latitude).
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Hp ENVY m6-010dx Notebook Windows 7 Driver Package SOLVED

    As many of you know, hp does not provide Windows 7 Drivers for many newer notebook models that shipped with either Windows 8 or 8.1. Some models, such as ProBook, do come with both Windows 7 and Windows 8 or 8.1 licenses and have thus hp provides drivers for both.
    The hp ENVY m6-010dx ships with Windows 8.1 installed and only has listed drivers for that operating system on the hp Support Site.  Many of the Windows 8.1 Drivers will work for Windows 7 - but some will not.
    I have complied a Windows 7 Driver (64bit) Package for the ENVY m6-010dx (my guess is it will also work on other slightly different ENVY Models with AMD Processors such as mine).
    If you have an hp ENVY m6-010dx and hate Windows 8.1 and want to downgrade to Windows 7 - here is the link to the driver package I have put together. It's a large file - well worth the download time though if you want to use Windows 7.
    https://www.dropbox.com/sh/01svwkhdi9n9crf/AABqObKTkDmU3g04gMfi0ky-a?dl=0
    Hope this helps others.
    Greg Griffin

    You're very welcome.
    Try this driver for the bluetooth from a Lenovo notebook...
    http://support.lenovo.com/en_US/downloads/detail.p​age?DocID=DS029104
    Try this wirless driver from asus:
    You wan the windows 7 file labeled :   (The first one listed)
    ASUS PCE-AC66 driver 6.30.95.26
    OS Support : Wins 7 (32&64)
    http://www.asus.com/Networking/PCEAC66/#support_Do​wnload_30
    Now you install this driver by unzipping the file you downloaded and make a note of the location of the unzipped file.
    Go to the device manager and click on the network controller needing drivers.
    Click on the driver tab. Click on Update Driver.  Select the Browse my computer for driver software and browse to the folder that was unzipped.
    Make sure the Include Subfolders box is checked and see if the driver installs that way.

  • Call to Driver Package Error - Nine Possible Solutions that have Resolved this Issue!

    Hello everyone I've decided to write up this guide to discuss and troubleshoot the “Call to Driver Package Error”.
    What is it ? What causes it?
    This issue normally occurs when a specific driver, that is being called, cannot be called. Sometimes, a 1627 or 1603 error is referenced in the error.
         - If a 1603 error is referenced, this indicates that an ERROR_INSTALL_FAILURE has occurred, meaning a component of the installation failed. This is normally accompanied when another form of installation occurs.
         - If a 1627 error is referenced, this indicates that an ERROR_FUNCTION_FAILURE has occurred, meaning a function at a specific moment has failed, and the installation cannot continue.
    Typically, these numbers do not mean a whole lot. However, for an advanced user, these numbers might mean a little bit more.
    An example?
    "Call to driver package install returned the error 1603 for Pkg C:/ProgramFiles\HP\HP officejet pro 8600\driverstore\ng scan driver\HPWia_OJ8600.INF"
    This is the most recent error message I've witnessed. If you break it down, you will notice that “HPWia_OJ8600.INF” is the installation file (INF) that has failed. WIA (Windows Image Acquisition) is crucial for scanning, and the printer installs this file to enable scanning features.
    How can you troubleshoot this error?
    This is the main portion of the post. I am going to suggest a significant list of troubleshooting that you can attempt. There are nine solutions which have resolved the issue in different situations, all of which I personally worked with. I'm hoping that these solutions will work for you if you have to face this error.
    *Please note that some of this troubleshooting is a little complicated. If a mistake is made, you may have to reinstall the operating system. However, the final troubleshooting step will require you to do this. You should make sure all of your data is backed up before troubleshooting.
    Backing Up Your Files (Windows 8)
    Backing Up Your Files (Windows 7)
    How to Back Up Your Files (Windows Vista or XP)
    You should also backup the Registry. There are some Registry-editing steps in the troubleshooting I provide.
    Backing Up, Editing, and Restoring the Windows Registry (Windows 8)
    Backing Up, Editing, and Restoring the Windows Registry (Windows 7)
    Backing Up, Editing, and Restoring the Windows Registry (Windows 98, ME, and XP)
    *After each step is attempted, you can try installing the printer software. If it fails, please uninstall the software before proceeding. This HP document will explain how to do it:
    1. The first step is performing a Clean Boot. I've resolved this issue in the past by performing this simple step before installing the software. A Clean Boot will turn off third-party programs and services that could be blocking the software from working correctly. For more information on how to do this, please look at this Microsoft document:
    How to perform a clean boot in Windows
    2. Next, make sure the Windows Installer it turned on and started. If it not, the installation may not complete. To do this, hold down the “Windows” and “R” key on the keyboard, which will open the Run box. In that box, type “services.msc” (without the quotes) and hit Enter.
    Now scroll down to the Windows Installer. If it is checked stopped, or not started, right-click on it and select “Start”.
    3. Next, I would suggest completing all Windows Updates:
    a) Open "Windows Update" in Control Panel.
    b) Click "Settings", and then click "Install optional updates".
    c) Next, click "Check for updates".
    This will ensure that all updates are found and installed. Once they are installed, see whether or not the error returns.
    4. If the issue is not resolved at this point, I would like to check the system for obvious corruption with an SFC scan. SFC stands for System File Checker, and it scans and attempts to restore corrupted Windows files.
    To do this, open Command Prompt as Administrator. Type in this command and hit Enter afterward: sfc
    /scannow
    Write down the results and restart computer after this completes.
    5. Creating a new Administrator account is a workaround to the issue. If the error does not appear on other accounts, this proves that whatever is causing the error is account-exclusive. I'm going to suggest you unlock the computer's built-in Administrator account.
    To do this, open Command Prompt as Administrator, again. Then type in this command and hit Enter afterward: net user administrator /active:yes
    6. The next step involves editing permissions in the Registry. In the Registry, please review the instructions below to apply full permissions to the following key: HKEY_LOCAL_MACHINE
    a) Right-click on the key that you need to edit and/or delete (HKEY_LOCAL_MACHINE). Click on "permissions..."
    b) Click "Add" in that Window that appears.
    c) There will be an empty box under "Enter the object names to select". Type "Administrator" (without the quotes), then click on "Check Names".
    d) An Administrator name will appear, click "Ok" when it does.
    e) You should be able to select (click) the Administrator profile under "Group or user names". Once clicked, click on "Advanced".
    f) Click on the "Owner" tab.
    g) Click on the Administrator profile, then put the check-mark in "Replace owner on subcontainers and objects".
    h) Go back to the "Permissions" tab, and ensure the Administrator profile is selected.
    i) In the "Permissions" tab, put a check-mark in every box available. The boxes will likely be indicated by "Include inheritable permissions from this object's parent" and "Replace all child object permissions with inheritable permissions from this object".
    j) Next, click "Edit". Put a check-mark in "Full Control" under Allow. Click Ok. Now, click Apply (you may receive a Window security message, just click "Yes"), then Ok.
    k) Exit the Registry, then restart the computer, and launch the Administrator account.
    7. The next step is to re-register the Windows Installer, and other dynamic library links (.DLL). Doing this will reference certain components that are required to complete the installation. Open Command Prompt as Administrator, then type each command and hit Enter after each one:
    MSIEXEC /UNREGISTER
    MSIEXEC /REGSERVER
    REGSVR32 MSI.DLL
    REGSVR32 ATL.DLL
    REGSVR32 SOFTPUB.DLL
    REGSVR32 WINTRUST.DLL
    REGSVR32 INITPKI.DLL
    REGSVR32 DSSENH.DLL
    REGSVR32 RSAENH.DLL
    REGSVR32 GPKCSP.DLL
    REGSVR32 SCCBASE.DLL
    REGSVR32 SLBCSP.DLL
    REGSVR32 MSSIP32.DLL
    REGSVR32 CRYPTDLG.DLL
    8. There are certain DLL files that can interfere with the installation, and they should be deleted. Go to C:\Windows\System32
    Delete the following files:
    HPZipm12.dll
    HPZinw12.dll
    9. Before reinstalling the operating system, you can try restoring it. This will allow you to return the computer to a point where the printer was working.
    *You should only do this if the software worked in the recent past.
    What is System Restore? - For Windows 7 and Vista
    How to refresh, reset, or restore your PC - For Windows 8 and 8.1
    What if these nine solutions do not work?
    Finally, you will need to reinstall the operating system if the issue is not resolved by this point. However, I can promise that this will resolve the issue. Here is a generic document on reinstalling the operating system:
    Overview of Recovering the OS or Reinstalling the Operating System
    And that's everything. Thanks for reading! - Mario
    I worked on behalf of HP.

    No error messages are given. It will either freeze while saying "Accessing iTunes Store," or without saying anything at all.
    I'd try the following document:
    Apple software on Windows: May see performance issues and blank iTunes Store
    (If there's a SpeedBit LSP showing up in Autoruns, it's usually best to just uninstall your SpeedBit Video Accelerator.)

  • NEW! 4.09 Soundstorm Audio driver package

    Okay,
    Guess that marriage is not the end of life so let me get again active in this forum
    So here is Markoul's debut in 2004...
    You did the Microsoft Windows Update to Audio driver for nf1/nf2 soundstorm driver version 4.09 and you ended up with a screwed Audio control panel?? (equalizer not working Environmental tab missing...etc)
    Simply run the driver package here,
    4.09 Soundstorm Audio driver package for nforce1/nforce2
    it uses the newest control panel version 4.08 in order to make the 4.09 audio driver fully operational
    enjoy,
    Markoul

    Hi,
    Crikey! I seem to update my audio drivers every couple of weeks. Here we go again!  
    Edit: I've just realised I've already got this one - nice feeling being one of the first (Guinea pigs???) for a change.  
    Axel  

  • Why I can delete a driver in a driver package that I have no "permission" on?

    Scenario:
    One CAS (CAS), one Primary Site, two users (User1 and User2)
    We create a Driver Package with some drivers on Primary Site.
    Set Security Scope for the created Driver Package that only could be seen by User1.
    Logon with User2, delete a driver under Driver node and that is a member of that Driver Package.
    Pop up a window with a button” Show References”, click the button, no reference shows up.
    Click OK, then the driver is deleted permanently and not available from User1 too.
    Then you may wonder:"Why can I delete the drivers in the driver package?"
    Reason:
    The Security Scope does not apply to every driver when you set that for a Driver Package. So User2 still has the right to delete a driver in that Driver Package. The pop-up window shows no reference because User2 has no permission to read the Driver Package.
    Workaround:
    There is no perfect workaround. If needed, you could set the permissions of Device Drivers to uncheck delete permission as shown in the picture below.
    However, please be aware of that, this user would be unable to delete ANY drivers under the Drivers Node.
    Reference:
    Planning for Security in Configuration Manager

    If you are using Lion the user Library folder is hidden.
    Finder > Hold down the option key and click Go on the menu bar. Then open Libary from the list.
    So User Library > Application Support > iWork > Numbers > Templates > My Templates.
    Finder in column mode is the easiest..

  • SCCM 2012 OSD; Not finding driver package during deployment

    I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction.  Specifically I am having trouble with device driver deployment while deploying my reference image. 
    I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image.  I am not sure if it matters, but I manually built a reference
    PC and using capture media (USB stick), I successfully captured my reference image.  I have imported my drivers for the target PC into Config Manager and into a driver package.  The driver package has been deployed to the distribution point
    (DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim.  Within the TS, I added an "Apply
    Driver Package" step and pointed it to the aforementioned driver package.  I added a WMI query to the step as follows
    select * from Win32_ComputerSystem where Model like "HP Probook 6570b%." 
    Incidentally, I did a wmi query on the target PC to verify the model.  I deployed the TS to the unknown computers collection and PXE booted the target PC.  I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
    the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found."  I checked the smsts.log log and found the following:
    Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
    After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
    for deployment.  After more research I have done the following:
    Deleted the Driver Package and recreated it and updated the TS step to point to this package.
    Deleted and recreated the TS along with the driver package.
    Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
    When distributing content I verified it was successfully completed each time as per the console.
    Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error.  If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
    and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
    I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
    Thanks in advance,
    Mike G.

    Thanks for responding.
    Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points.  I checked now (about 12 hours later) and the package is showing it has not finished updating.  I checked the content status and
    it is "waiting for content."  I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1".  This error would occur every 30 min after each time the DP retried to process
    the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
    it retried, the error cleared, however the package status is still waiting for content.  I tried doing a validation on the package but so far there has been no change.

  • SCCM 2012 R2 Driver - Best Practices on Updating Driver Packages?

    Example the new Surface Drivers were Release We are currently using September what is the best way to update the drivers?  If Import it shows multiple drivers old and new...  Thoughts?  Blog Post?

    No. You must always import drivers to be able to either one of the Apply Driver task types in a task sequence.
    However, you can also run a driver installer provided by the vendor as a package because the driver installer is a generic exe that does whatever its supposed to do outside the control of ConfigMgr.
    Note that although you can't use an Auto Apply Driver task in stand-alone media, you can absolutely use an Apply Driver Package in stand-alone media. In general, most folks do not rely on Auto Apply but instead rely on Apply Driver Package for multiple reason.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • How can I download a Complete Driver Package for L500-20X

    Hello
    on the Toshiba Driver Page i only found Single Drivers and i must Download to much as Single Files.
    How can i Download a Complete Driver Package as ZIP/RAR or Image DVD or CD.
    I dont want to Download 30 or 40 Single Drivers for my Toshiba , one Download for all please , because other Companys makes this allready like F.Siemens, HP , Dell or else.
    Thanks

    While I do agree that some of the other manufacture's have a more convenient way to download the drivers, I still question your eroneous assumption that you need to download 500 different files. EVERY DRIVER, UTILITY, and APP file you need are already on your laptop. All you need to do is create your Recovery Disks and you have a complete set of them ready to install when needed. And no, they aren't just part of the recovery images forcing you to install the factory image, but individual files that can be installed to any install of the same OS type which means you wouldn't need to download anything at all to get back up and running if you install a new hard drive. You would only need to download drivers if you upgrade to a different OS.
    Now consider that for the most part the drivers offered from Toshiba aren't the latest version anyway, most Power Users are going to download the drivers from the chipset manufacture's support site anyway as they are newer and provide better performance who really cares if Toshiba offers a single download anway.
    That's my take on the matter. Your mileage may differ.
    If you don't post your COMPLETE model number it's very difficult to assist you. Please try to post in complete sentences with punctuation, capitals, and correct spelling. Toshiba does NOT provide any direct support in these forums. All support is User to User in their spare time.

  • Captured & imported image, and driver package not going to DP

    I have an image I've imported and even though I've selected "Distribute Content" manually it does not go to DP.   I checked everything I could think of (making sure DP was set to service the boundary group, etc.), but it still won't go.  
    In status, it says "in process".  
    Question - do I need image/properties/package share settings "copy the content in this package to a package share on distribution points" selected to enable this image to be sent to the DP?
    Under Distribution Settings - do I need to select "Distribute the content for this package to a preferred DP..." and any recommendations on if this should be sent to Automatically, Download only changes, or Manual?
    Similarly, I also noticed my Driver Package had also not been sent to the DP, so my question applies to that as well.  After creation, do these settings need to be selected?
    Thank you
    Nathan

    Hi,
    The reason why this happens is a combination of the following two reasons:
    - You enabled for prestaged content in the distribution point.
    - Go to the properties of the image, on the "Distribution Settings" tab the radio button is set to "Manually copy this content to the distribution point".
    Enabling the prestaging option on a DP will tell the DP to not receive content automatically. It is waiting until an administrator copied *.pkgx files manually to it and registers them using extractcontent.exe. That might be useful for DPs at the end of very
    small WAN links. 
    For more infomation, please review the link below:
    Operations and Maintenance for Content Management in Configuration Manager
    http://technet.microsoft.com/en-us/library/gg712694.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Where are stored Driver Packages on SCCM 2012?

    When you create a driver package, you must select directory where manufacture drivers are stored. This directory has got *.inf, *.sys, *.exe, *.msi....etc...but SCCM only find *.inf
    The questions are:
    - Does SCCM put all these files on SCCM database or only *.inf files ?
    - What happend with dependencies with other files?

    Hi, When you say "distribute to your distribution points" does this have to be to ALL distribution points ?
    Im using Fallback for scource content, and i have noticed that there is no option to allow Driver Packages to be deployed from FallBack Source Localtions.
    So my question i suppose is.. do driver packs have to be placed on ALL distribution points even if you have a fallback source location. ?
    Cheers

  • When Other Realtek Driver Packages Fail...

    There have been a number of posts, where problems with APE have been solved
    by reloading the REALTEK audio interface drivers.
    When Other Realtek Driver Packages Fail...
    try this one:
    AUD_ALLOS_XP_VISTA_5377_PV_REALTEK.EXE
    from:
    http://downloadcenter.intel.com/download.aspx?url=/11597/eng/UAA.zip&DwnldId=11597&lang=en g
    This is actually a composite of a number of fixes and updates from both
    Realtek and Microsoft. It is especially useful when other driver packages,
    including the current High Definition Driver package from Realtek's site,
    fail to load properly.
    Errors addressed include red and yellow error flags on the high definition
    audio driver entry in XP's device manager, and a PCI device that won't load
    a driver because an appropriate driver can't seem to be found.
    I ran into these problems when trying to upgrade an existing
    fully-configured XP system to a new motherboard. The audio driver provided
    by the motherboard vendor wouldn't load, and neither would the
    latest-greatest one from Realtek's site.
    As always, if your system is working OK right now, don't try to fix it!

    Though not specific to Realtek chips, there is also a little add-on, that has saved a lot of people with all flavors or Premiere, Audition and SounBooth - the freeware ASIO4All. This applet installs and sets up an ASIO environment that by-passes some of the problem areas encountered when trying to set up Audio with just the chip/card's driver. Once installed, it will appear in the ASIO settings list, or drop-down, depending on program. One has to point to it for all ASIO interfaces. Do not forget any other programs with Audio, such as Audacity, Magix Music Studio, etc.
    Hunt

  • Am I missing a windows driver package? if so, how do I download it?

    I think I accidentally deleted one of the 'windows driver package' and now I cant use my right click on my touchpad. I used to be able to select a folder by clicking anywhere on the touchpad but now I have to use left click. any ideas on how this might happen and how to fix it?
    I am using bootcamp 3.1 on os snow leopard

    Can you "restore" it back prior to the time you think you deleted the drivers? (Control Panel/ Backup and Restore)
    If you have a back up you should be able to install it from there? You might try installing from the Boot Camp driver folder and install the touchpad drivers manually and see if that helps. You should also try the Apple Software updater in Windows and let the Boot Camp drivers get updated to 3.0.4 also.

  • Issue regarding Thin Installer and driver packages

    Hello everybody,
    I have recently started to work for a new company and have been tasked with creating a new Windows deployment solution.
    My company are using Lenovo desktop and laptop and my installation image use Thin Installer to deploy drivers to our workstations during Windows deployment.
    I have been having some difficulties getting everything to work and I want to write about it here to hopefully help someone in the same situation as me and call out for better quality control at Lenovo.
    Here are the command line I call to start Thin Installer from the local computer:
    START /WAIT thininstaller.exe /CM -search A -action INSTALL -repository \\wds\lenovo -noicon -showprogress -IncludeRebootPackages 1,3,4  -noreboot
    Hers the issues I have expirienced:
    1. Sometimes packages downloaded with Update Retriever will be set to "Reboot type: Forces a reboot" as default. This causes the Thin Installer to reboot reguardless of the -noreboot switch.
    Its possible to change reboot type "Requires a reboot" in Update Retriever and than the updates installs fine.
    This causes problem with scripted installs where you cannot have the system reboot "out of order".
    Updates should never be default "forces a reboot".
    2. On my Thinkcenter e93z (10B8) the Intel Displaydriver (v 9.18.10.3220) wont install because the PnPID is not listed in the XML file. (my PnPID is VEN_8086&DEV_041E&SUBSYS_309C17AA (309D17AA is listed tho)). Manualy editing the XML files to include my PnPID solves the problem.
    Lenovo should really have better qualitycontrol here.
    3. On a t440s machine i have the Synaptics UltraNav Driver (v. 17.0.12.60) wont install automatically with Thin Installer.
    This is because the machine i installed failed the "BIOS test" in the XML file of the update package. I manually edited the XML file and replaced the "BIOS TEST" with one from another update that worked on that system and now everything installs automatically and works fine.
    Its possible that Lenovo has detected some kind of problem with my BIOS version and the Synaptics driver but everything seems to work fine for me.
    I hope this post will help someone in the future
    EDIT: Other people have called out some problems with the information provied in this post. You should read the whole thread before making any changes to your systems.
    Kind Regards,
    2bi

    2bi,
    Thanks for posting your findings.  I will investigate and escalate the missing PnP id issue for the Display Driver issue.  We absolutely need to avoid these kinds of escapes.
    For you ThinInstaller command line I would recommend not using the -showprogress parameter if you are using in a scripted deployment scenario with something like MDT and/or SCCM.  These solutions typically will not allow TI to interact with the desktop during deployment which is what -showprogress will cause.
    Also, you are telling TI to include packages that will automatically reboot your system (type 1), requires a reboot which can be delayed (type 3), will shutdown the machine automatically (type 4).  We have very few type 4 packages anymore; however we definitely have type 1 and type 3.  As sclexman mentioned, the -noreboot will only apply to the type 3 packages which leave the execution of the reboot up to TI.  So -noreboot tells TI that even if it installs updates of type 3, it should not reboot when finished.
    Changing the Reboot Type value in Update Retriever only changes how TI sees the package and does not alter how the package itself executes.  So if a package is designed to always automatically reboot, changing it to type 3 in UR will have no affect.  We have recently had a display driver released by Intel that will automatically reboot if the driver installer detects that it is upgrading an older version of the driver.  In a clean deployment scenario, the automatic reboot will not happen so in this case it is safe to change the type to type 3.
    This leads to another point.  All of our content that is available through Update Retriever is also intended for consumption by System Update which is the utility aimed at individual consumers to help them keep their drivers up to date.  Therefore this becomes our lowest common denominator that we have to support.  This leads to situations that may not be ideal for the deployment scenario.  If we had an army of resources we might be able to manage all of our content for both consumers and enterprise deployments; in effect doubling our efforts.  Unfortunately this is not the case and we are trying to do the best we can.
    Regarding the UltraNav update for T440s, I see that the XML has a _BIOS section under the Dependencies.  However it is defined such that any BIOS level will work because the first level listed is a wildcard asterisk (*).  This BIOS section is actually included for a completely different solution which also uses the XML.  It is not intended to control the targeting of the update for System Update or Thin Installer.  Perhaps there was a mistake made initially and the XML was released without the * and has since been fixed.
    (from the current UltraNav driver package:  )
    <_Bios>
    <Level>*</Level>
    <Level>GGET*</Level>
    <Level>GFET*</Level>
    <Level>GHET*</Level>
    <Level>GIET*</Level>
    <Level>GJET*</Level>
    <Level>GLET*</Level>
    <Level>GMET*</Level>
    <Level>GNET*</Level>
    <Level>GRET*</Level>
    </_Bios>

Maybe you are looking for