Ads Usb Driver

by



Learning has never been so easy!

Windows 10 Compatibility If you upgrade from Windows 7 or Windows 8.1 to Windows 10, some features of the installed drivers and software may not work correctly. Android Debug Bridge (adb) is a versatile command-line tool that lets you communicate with a device. The adb command facilitates a variety of device actions, such as installing and debugging apps, and it provides access to a Unix shell that you can use to run a variety of commands on a device.

Recently I came across a problem when attempting to install Windows 7 onto a Dell Precision 7710. I would boot up with a DVD that had an .iso image of Windows 7 installed on it, but when after clicking the install windows button, I would get a notice that the installer couldn't locate the CD/DVD driver and I needed to browse to locate it. Well, I thought I would be smart and instead do the install via a USB device. Same error. Well, how does this make sense? It's asking for a DVD driver when using a USB device. That's like your car throwing a CEL for the carburetor not working when you're using fuel injection.

This issue is caused because the installer media doesn't have a driver to install through a USB 3.0 port. You might ask, well why did the DVD drive throw the error? Well, that's because the DVD drive was an external because there is no internal DVD drive on this model laptop. So I now know my problem. USB 3.0 drivers need to be added to the boot media. Follow this guide and I'll show you how to accomplish this using the CMD line and the DISM utility.

9 Steps total

Step 1: Download the USB Drivers

Ad net usb driver

Now, I had all intention of describing this how-to specifically for adding USB 3.0 drivers, but it can also be used for adding any number of drivers to the boot media as well.

Driver

First thing you're going to do is to download the USB drivers from either your computer's manufacturer or from your motherboard's manufacturer. With the Dell Precision 7710 I went to http://www.dell.com/support, punched in my service tag number and proceeded to download an entire driver pack in .CAB format.

Step 2: Extract the drivers

Depending on the type of file you downloaded, it could be an .exe, a .cab, or a .zip, so you'll need to unzip the drivers out of this file. Driver files are historically mainly .inf files, but you don't need to pick and choose the individual files because this next process makes it automatic for you. The DISM (Deployment Image Servicing and Management Tool) is smart and will automatically grab the correct files.

1. Create a folder on your desktop named 'Drivers'.
2. Create two folders inside of the 'Drivers' folder, 'mount' and 'USB'.
3. Extract or copy/paste the driver files directly into the 'USB' folder. I used 7-zip to extract my driver files directly into the 'USB' folder.

Step 3: Cut the 'boot.wim' and 'install.wim' files

Locate these two files from within your boot media. This is easy if you are using a USB drive instead of a DVD, so that you don't have to reburn the DVD once we finish modifying these files.

Example: If the USB drive is plugged in and has been given drive letter 'P:' you will locate the 'boot.wim' and 'install.wim' files within the path: P:sources

Ads Usb Driver

It is best to just cut them out of the install media, but if you want to have a backup copy you can copy and paste. You are pasting into the 'Drivers' folder on the desktop. Just make sure to overwrite the old files with the new updated ones once we're finished with this process.

Step 4: Open up CMD prompt as Administrator and navigate to the 'Drivers' folder on the desktop

Windows 7:
1. Start, type in cmd, right click on the icon and choose Run as Administrator
Windows 8:
1. Windows Key + Q
2. Move mouse to top right corner and search, type in Command Prompt, Right click and Run as Administrator.

Next, you will need to change the directory path so that it isn't pointing to the default of C:WindowsSystem32.

Type in: cd C:Users%currentuser%DesktopDrivers - Then press Enter.
*Note: Make sure to change the %currentuser% to that of the user profile where the 'Drivers' folder was saved.

Software

Step 5: Update the 'boot.wim' file.

In the cmd line now displaying the cd pointing to the right directory, type in these commands pressing enter after each one.

dism /mount-wim /wimfile:boot.wim /index:2 /mountdir:mount
Explanation: This command mounts the boot.wim file, index points it to the correct boot parameters for the correct OS, and /mountdir:mount points it to mount the file to the 'mount' folder we created in this directory earlier.

dism /image:mount /add-driver:'USB' /recurse
Explanation: This command automatically grabs the driver files that it locates in the 'USB' folder that we created earlier and copied the drivers to. This can take a while depending on the number of driver files that it locates.

dism /unmount-wim /mountdir:mount /commit
Explanation: This command unmounts the boot.wim file and saves the information. Think of this as a file transfer/compression process.

Step 6: Determine which index you're going to update the driver files for on the 'install.wim' file

This process wasn't necessary on the 'boot.wim' file, but it is in the 'install.wim' file. Each version of Windows can have a specific index number and we will need to locate which one it is in order to issue the command for the version of Windows you plan on installing. This is specific to the install media you are using because some install media only comes with one version of Windows 7, such as Professional, but some others may have multiple version of Windows 7, such as Home, Ultimate and Professional, just to name a few.

Issue the following command to determine what your version is:

dism /Get-WimInfo /WimFile:install.wim

You'll see in the screenshot that I have an index of 1.

Step 7: Update the 'install.wim' file.

You should still be pointed to the correct directory, so now issue the following commands to update the 'install.wim' file, using the index information you got from the step above.

dism /mount-wim /wimfile:install.wim /index:1 /mountdir:mount
Explanation: All exactly the same as the boot.wim file command, except the index is the only difference.

dism /image:mount /add-driver:'USB' /recurse

dism /unmount-wim /mountdir:mount /commit

Step 8: Cut/Paste or Copy/Paste your new 'boot.wim' and 'install.wim' files

Since I used the Cut/Paste method to remove these two files from the P:sources location, I'm going to do the same to remove them from the C:Users%currentuser%DesktopDrivers folder and place them back into the P:sources folder.

Wait for the transfer to finish. This is going to take a little bit longer to copy back over to the flash drive because the files going back in are larger than they were before due to the driver files that you've added to it.

Ads Usb Driver

Step 9: You're Done!

Take out the flash drive and pop it into the machine you want to reinstall Windows 7 on. You should now find that you no longer receive the pesky CD/DVD driver missing notice.

Thank you all for reading through this. These commands can be adapted to suit whichever folder names you want to use. Good luck!

Published: Jan 20, 2016 · Last Updated: Nov 06, 2017

107 Comments

  • Thai Pepper
    Capef3ar Jan 28, 2016 at 06:39pm

    Nice read - haven't run across this yet but good info to have just in case. Thanks!

  • Tabasco
    bethernet Mar 17, 2016 at 10:56pm

    THANK YOU! I only wish I had found this 3 hours ago... It worked exactly as your directions said it would, and Windows 7 is installing now!

  • Pimiento
    jimnowotny Apr 4, 2016 at 02:48pm

    Thanks! The problem with an older OS and really new hardware.

  • Pimiento
    hmasri Apr 13, 2016 at 05:28am

    If its just USB 3.0 drivers for Win7 you want ...

    https://downloadcenter.intel.com/download/25476/Windows-7-USB-3-0-Creator-Utility

    5ryn

  • Sonora
    MrMcG33k Jun 7, 2016 at 04:26pm

    Thank You! I just ran into this issue and this resolved my problem!

  • Pimiento
    nicoserup Jun 10, 2016 at 08:43pm

    Question for point 6:
    In my Windows image, I have unlocked all the versions, so which one should i pick?
    - I haven't tried the guide yet though.

  • Poblano
    palehmkuhl Jun 13, 2016 at 01:22pm

    Choose whichever version that you plan on installing Windows with.

  • Pimiento
    nicoserup Jun 16, 2016 at 02:41pm

    It doesn't work for me yet.
    In my version I have unlocked all of the versions, starter to ultimate.
    I chose to mount it to proff.
    But when i boot, I never get as far as to choose which windows version I want, before the message: Missing CD/DVD comes.

  • Poblano
    palehmkuhl Jun 16, 2016 at 03:16pm

    Ok, so you're booting into the Windows ISO using your image on a bootable USB drive and that's when you're getting the message about it missing the CD/DVD drive. Sounds like something didn't go as planned if you did the process I outlined above. Either that or the driver that you added to the USB drive isn't the right one for that computer.

  • Pimiento
    scotthowell Jun 16, 2016 at 03:39pm

    For some reason I'm unable to mount the install.wim. When i try to run dism /mount-wim /wimfile:install.wim /index:1 /mountdir:mount I get an error: 5 'access is denied' error no matter which index I use.

  • Poblano
    palehmkuhl Jun 16, 2016 at 04:14pm

    Did you run the command line as an administrator during this process?

  • Pimiento
    scotthowell Jun 16, 2016 at 05:53pm

    Yes, and the boot.wim worked just fine. I am using a Dell proprietary Win7 installation image, though.

  • Poblano
    palehmkuhl Jun 16, 2016 at 06:02pm

    That might have something to do with it. I used a Win7 image that I downloaded from the Microsoft VLSC website. Generic. I don't believe this process is restricted to specific images, but you want to have the access to modify files in those directories. Try using a different Win7 bootable and see if you get different results.

  • Pimiento
    mikemccormack Jun 20, 2016 at 04:45pm

    Excellent KB...worked flawlessly - thank you for posting this!

    Have a great week!

  • Pimiento
    christernordell Jun 29, 2016 at 03:35pm

    scotthowell: I experienced the same problem getting error 5 when mounting install.wim. Found out its McAfee that is blocking, see https://kc.mcafee.com/corporate/index?page=content&id=KB76867. Deactivate McAfee during the mounting of install.wim solved the problem for me.In my case I had a rule that stopped handling .scr files and the mounting stopped when it reached the file bubbles.scr.

  • prev
  • 1
  • 2
  • 3
  • 4
  • 5
  • ...
  • 8
  • next
Google is committed to advancing racial equity for Black communities. See how.

The Google USB Driver is required for Windows if you want to performadb debugging with Google devices. Windows drivers forall other devices are provided by the respective hardware manufacturer, as listed in theOEM USB Drivers document.

Note:If you're developing on Mac OS X or Linux, then you do not need to install a USBdriver. Instead seeUsing Hardware Devices.

You can download the Google USB Driver for Windows in one of two ways:

  • Or, get it from the Android SDK Manager as follows:
    1. In Android Studio, click Tools > SDK Manager.
    2. Click the SDK Tools tab.

    3. Select Google USB Driver and click OK.

      Figure 1. The SDK Manager with the Google USB Driver selected

    4. Proceed to install the package. When done, the driver files are downloaded into the android_sdkextrasgoogleusb_driver directory.

    Using the SDK Managerhelps you keep the driver up to date by notifying you when your current driveris out of date.

For installation information, readInstall a USB Driver.

Download the Google USB driver

Before downloading, you must agree to the following terms and conditions.

Terms and Conditions

This is the Android Software Development Kit License Agreement

1. Introduction

1.1 The Android Software Development Kit (referred to in the License Agreement as the 'SDK' and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK.1.2 'Android' means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: https://source.android.com/, as updated from time to time.1.3 A 'compatible implementation' means any Android device that (i) complies with the Android Compatibility Definition document, which can be found at the Android compatibility website (https://source.android.com/compatibility) and which may be updated from time to time; and (ii) successfully passes the Android Compatibility Test Suite (CTS).1.4 'Google' means Google LLC, organized under the laws of the State of Delaware, USA, and operating under the laws of the USA with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA.

2. Accepting this License Agreement

2.1 In order to use the SDK, you must first agree to the License Agreement. You may not use the SDK if you do not accept the License Agreement.2.2 By clicking to accept and/or using this SDK, you hereby agree to the terms of the License Agreement.2.3 You may not use the SDK and may not accept the License Agreement if you are a person barred from receiving the SDK under the laws of the United States or other countries, including the country in which you are resident or from which you use the SDK.2.4 If you are agreeing to be bound by the License Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.

3. SDK License from Google

3.1 Subject to the terms of the License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable, non-exclusive, and non-sublicensable license to use the SDK solely to develop applications for compatible implementations of Android.3.2 You may not use this SDK to develop applications for other platforms (including non-compatible implementations of Android) or to develop another SDK. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose.3.3 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. 'Intellectual Property Rights' means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you.3.4 You may not use the SDK for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK.3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement.3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you.3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features.3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the SDK.

4. Use of the SDK by You

4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications.4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so.4.4 You agree that you will not engage in any activity with the SDK, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of any third party including, but not limited to, Google or any mobile communications carrier.4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so.4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.

5. Your Developer Credentials

5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.

6. Privacy and Information

6.1 In order to continually innovate and improve the SDK, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the SDK are being used and how they are being used. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected.6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in accordance with Google's Privacy Policy.6.3 Anonymized and aggregated sets of the data may be shared with Google partners to improve the SDK.

7. Third Party Applications

7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources.7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners.7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. In that case, the License Agreement does not affect your legal relationship with these third parties.

8. Using Android APIs

8.1 Google Data APIs8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service.8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. If you use the Android Recognition Service API, documented at the following URL: https://developer.android.com/reference/android/speech/RecognitionService, as updated from time to time, you acknowledge that the use of the API is subject to the Data Processing Addendum for Products where Google is a Data Processor, which is located at the following URL: https://privacy.google.com/businesses/gdprprocessorterms/, as updated from time to time. By clicking to accept, you hereby agree to the terms of the Data Processing Addendum for Products where Google is a Data Processor.

9. Terminating this License Agreement

9.1 The License Agreement will continue to apply until terminated by either you or Google as set out below.9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the SDK and any relevant developer credentials.9.3 Google may at any time, terminate the License Agreement with you if:(A) you have breached any provision of the License Agreement; or(B) Google is required to do so by law; or(C) the partner with whom Google offered certain parts of SDK (such as APIs) to you has terminated its relationship with Google or ceased to offer certain parts of the SDK to you; or(D) Google decides to no longer provide the SDK or certain parts of the SDK to users in the country in which you are resident or from which you use the service, or the provision of the SDK or certain SDK services to you by Google is, in Google's sole discretion, no longer commercially viable.9.4 When the License Agreement comes to an end, all of the legal rights, obligations and liabilities that you and Google have benefited from, been subject to (or which have accrued over time whilst the License Agreement has been in force) or which are expressed to continue indefinitely, shall be unaffected by this cessation, and the provisions of paragraph 14.7 shall continue to apply to such rights, obligations and liabilities indefinitely.

10. DISCLAIMER OF WARRANTIES

10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SDK IS AT YOUR SOLE RISK AND THAT THE SDK IS PROVIDED 'AS IS' AND 'AS AVAILABLE' WITHOUT WARRANTY OF ANY KIND FROM GOOGLE.10.2 YOUR USE OF THE SDK AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SDK IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE.10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

11. LIMITATION OF LIABILITY

11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.

12. Indemnification

12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the SDK, (b) any application you develop on the SDK that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you with the License Agreement.

13. Changes to the License Agreement

13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.

14. General Legal Terms

14.1 The License Agreement constitutes the whole legal agreement between you and Google and governs your use of the SDK (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the SDK.14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google.14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable.14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement.14.5 EXPORT RESTRICTIONS. THE SDK IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE SDK. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE.14.6 The rights granted in the License Agreement may not be assigned or transferred by either you or Google without the prior written approval of the other party. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under the License Agreement without the prior written approval of the other party.14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction.January 16, 2019

latest_usb_driver_windows.zip