cdob

What about http://update.microsoft.com/windowsupdate ?

As for USB controller and USB hub: Dism does a good job, the driver files are copied to driverstore and to system32\drivers. In addition there are included to the registry CriticalDeviceDatabase. And to Services, marked to demand Start=3. The drivers are working at next boot. However a existing ENUM entry has a higher priority. If a relating ENUM entry exist, but without a service entry, then the drivers are not connected to the hardware, they are not used. Delete the half broken ENUM entry. Or try to add iusb3xhci und iusb3hub to the ENUM entry. Dism and regedit are sufficient to adjust Hardware in machine to new machine.

Did you boot the Windows 7 from other hardware at the new hardware once? The USB 3.0 controller is marked alerady, but no driver connected. Do you have the a old Windows 7 image, not booted at the new hardware? Can you restore this old image? Then run dism.exe again and inlcude iusb3xhci and iusb3hub again. (include relating x86 or x64 drivers) No need for the the switch driver, the given chipset connects the USB 3.0 ports to the xhci controller always. Do you get USB mouse and keyboard now? Or the other case: Windows 7 form other hardware once booted at new hardware: Dism.exe did include the dricers correctly. But the device manager waits for a user confirmation to install the new driver. Delete certain USB 3.0 settings from previous boot. Boot a WinPE (e.g. a installation DVD and press shift F10) Run regedit, import the Windows 7 from other hardware system hive to Win7_harddisk: HKLM\Win7_harddisk Read HKLM\Win7_harddisk\Select\Current HKLM\Win7_harddisk\Select\Default Are both values 0x1? Then goto HKLM\Win7_harddisk\ControlSet001\Enum\PCI Search CC_0C0330 Delete the parent HKLM\Win7_harddisk\ControlSet001\Enum\PCI\VEN_8086&DEV_* entry Unlod the hive HKLM\Win7_harddisk. Boot to Windows 7.

Well, let's rephrase: The convenience rollup creates a secenario: updates are pending This is the weird reason monthly rollup isn't recognized and is still being offered by Windows Update. The error source is the convenience rollup, not the monthly rollup. The convenience rollup is the problem. The documented work aound uses a (virtual) live system. Reboot and install the monthly rollup. Sysprep the patched machine and capture an new install.wim file. The monthly rollup is integrated fully then. Clarify the main question: Integrate the monthly rollup, no matter how it's done? Integreate the monthly rollup to a offline image, using which tools?

The the huge convenience rollup requires a reboot to install fully. Windows 7 refreshed media creation https://blogs.technet.microsoft.com/astoica/2017/01/03/windows-7-refreshed-media-creation/

I understand: Intel Hub connected to a Intel USB Hub. And next to a Intel USB 3.0 controller USB\VID_045B&PID_0209 USB\VID_8087 Renesas Hub connected to a Intel USB Hub. And next to a Intel USB 3.0 controller USB\VID_2109&PID_2811 There is a issue with both Intel Hub and Renesas Hub. There are no Intel USB 3.0 XP drivers. There are Renesas USB 3.0 Hub XP drivers, but they are tested with Renesas controller drivers. A Renesas USB 3.0 Hub XP driver may work with a XP default controller drivers, or may fail. Verify the BIOS section 5-2-7 USB Blocker. Does the BIOS prohibit the USB Mass Storage Device by disabling the USB hub? Did you disable USB 3.0 xhci mode at BIOS? It's a BIOS or a driver issue. It's working at a reboot, but not at a power down and power up? Guessed: it's the BIOS. The BIOS expect proper OS USB 3.0 drivers, there are no XP drivers. Try a PCIe USB 3.0 card, with XP driver support.

@Damnation Don't you use a GA-Z97X-UD5H-BK? The manual describes BIOS section 5-2-7 USB Blocker. Are any USB devices blocked? I don't understand the Product Specification: USB Chipset: - 4 x USB 3.0/2.0 ports (2 ports on the back panel, 2 ports available through the internal USB header) - 6 x USB 2.0/1.1 ports (2 ports on the back panel, 4 ports available through the internal USB headers) Chipset + Renesas uPD720210 USB 3.0 Hub: - 4 x USB 3.0/2.0 ports on the back panel The picture shows 8 ports on the back panel. 2 ports and 2 ports and 4 ports are 8 ports on the back panel. Is the Renesas uPD720210 USB 3.0 Hub connected to a Intel USB 3.0 controller? How does USB 2.0 USB 3.0 handshake works at XP with XP default drivers? https://www.renesas.com/en-us/products/usb-assp/upd720210.html How does the motherboard block USB devices? Are enabled and disabled relating USB Hubs? Is USB\VID_045B&PID_0209 a real HardwareID or a fake ID created by the BIOS? http://www.driveridentifier.com/scan/generic-usb-hub/driver-detail/8E4E9F8C50CA4AFA86F6DC47B21B9148/1036412/156090eb6d87a3a004396b94e49e61e2/1238316339/USB-CLASS_09 Are there different motherboard revisions? Do you have USB 2.0 slot brackets? Can you connect this to the internal USB headers? Goto device mangager, change view per connection. Which USB controller precedes the USB hub?

Edit Windows7-x64\k11acw7\netathr7x.inf [Manufacturer] ;%ATHEROS% = Atheros, NTamd64.6.1 %ATHEROS% = Atheros, NTamd64 ;[Atheros.NTamd64.6.1] [Atheros.NTamd64] The Windows 7 binary driver may work or fail at Vista.

Go back to AHCI mode temporarily. Boot Windows 7, open the registry HKLM\system\CurrentControlSet\services\pciide set start=0 Enable IDE mode again.

The BIOS shows two active XHCI controllers. I understand: The BIOS dosn't allow do disable xhci mode. XHCI hand-off is about switching USB 2 or USB 3 mode. Do not install Intel USB 3 drivers. If you are lucky, default Vista USB 2 drivers are active.

This are ASMedia drivers, not Intel drivers. There are different USB contollers at the motherboard. One chipset Intel USB 3.0 controller and another ASmedia USB 3.1 controller. Guessed: there are USB 3.0 ports and USB 3.1 ports at the laptop. There are ASmedia USB 3.1 Vista drivers. There is a inf section [ASMEDIA.ntamd64] Intel dosn't provide USB 3.0 Vista drivers. There is a inf section [Intel.NTAMD64.6.1], Windows 7 and up Disable Intel xhci at BIOS, fix to USB 2.0.

http://www.intel.com/content/www/us/en/support/boards-and-kits/000005506.html Intel USB 3.0 eXtensible Host Controller Driver Not Supported in Windows XP or Windows Vista

No need for a additional tool. The OS itself lists the ACPI key. The key is a key, it's not a usage permission. https://answers.microsoft.com/en-us/windows/forum/windows_10/windows-10-this-product-key-didnt-work-please/95a7e9cd-077f-40d6-b3df-028f8c41303a?page=2 wmic path softwarelicensingservice get OA3xOriginalProductKey The OS manufacturer lists two different cases: https://www.microsoft.com/en-us/useterms How is the software aquired? From a store as packaged software for end-users of from Microosft directly? Pre-Installed on your computer from the computer manufacturer? The first Windows 8 OEM is tranferable to another computer, the second is not. This is the manufacturer opinion. In addition there are local laws. A packaged software for end-users is clearly transferable. The Pre-Installed version is questionable to transfer.

The manufacturer opinion is: http://personaluselicense.windows.com/en-US/default.aspx To make that transfer, you must transfer the original media, the certificate of authenticity, the product key and the proof of purchase directly to that other person, without retaining any copies of the software. At a hardware manufacturer Windows 8 OEM the product key is embedded in BIOS, you don't know he product key, you don't have to know the key to install a new Windows. You can not transfer the key without retanining any copies, as long you keep the hardware. This OS manufacturer opinion relates to en-US system builder OEM version only. Not to a hardware manufacturer OEM version. Transfering a system builder OEM is allowed, a hardware manufacturer OEM transfer is not specified at above link. There are different countries with different laws and court rulings. There are a lot of different cases, there is no general answer to license transfer.

The download works for retail key version only, not at OEM versions. https://www.raymond.cc/blog/links-for-windows-7-sp1-iso-from-microsofts-official-distributer/ Read sections Download Windows 7/8.1 from The Windows 10 Download Page and Download a Windows 7 or 8.1 ISO Without JavaScript

Can you clarify the request? Do you like to add drivers? Do you like to replace active drivers? Can you name some examples? Which hardware do you use and which drivers are missing? Dism can add drivers to a offline Windows. But the drivers are not installed fully. Boot critical drivers are available at next boot. Windows may install non boot criticical drivers at next boot. https://technet.microsoft.com/en-us/library/hh825070.aspx

Enable Testsigning mode and edit the inf file: [Manufacturer] %Intel% = IntelGfx, NTamd64 [IntelGfx.NTamd64] %iCNTG0% = iCNT0, PCI\VEN_8086&DEV_2A42 %iCNTG1% = iCNT1, PCI\VEN_8086&DEV_2A43 %iEGLG0% = iEGL0, PCI\VEN_8086&DEV_2E02 %iEGLG1% = iEGL1, PCI\VEN_8086&DEV_2E03 %iEGLQ4G0% = iEGL0, PCI\VEN_8086&DEV_2E12 %iEGLQ4G1% = iEGL1, PCI\VEN_8086&DEV_2E13 %iEGLG4G0% = iEGL0, PCI\VEN_8086&DEV_2E22 %iEGLG4G1% = iEGL1, PCI\VEN_8086&DEV_2E23 %iEGLGVG0% = iEGL0, PCI\VEN_8086&DEV_2E32 %iEGLGVG1% = iEGL1, PCI\VEN_8086&DEV_2E33 %iEGLGB0% = iEGL0, PCI\VEN_8086&DEV_2E42 %iEGLGB1% = iEGL1, PCI\VEN_8086&DEV_2E43 %iEGLGBU0% = iEGL0, PCI\VEN_8086&DEV_2E92 %iEGLGBU1% = iEGL1, PCI\VEN_8086&DEV_2E93

Backup Activation Method http://unattended.msfn.org/unattended.xp/view/web/29/

Windows 7 doesn't support USB boot. Contrary there are some USB boot hints: http://technet.microsoft.com/en-us/library/ee731893(WS.10).aspx Timeout for boot device increase for Hyper-V Server 2008 R2. Read the BIOS / UEFI conditions influences USB boot possibility. http://msdn.microsoft.com/en-us/library/ff794567.aspx BootDriverFlags and PollBootPartitionTimeout for Windows 7 Embedded. Windows 8 does support USB boot. BootDriverFlags and PollBootPartitionTimeout are used to enable this. A default Windows 7 contains settings BootDriverFlags and PollBootPartitionTimeout. Both settins are disabled by default. Windows 7 kernel, hal and drivers are prepared for USB boot. But it's not a documented feature, may work or fail. fix_USB3_SD.cmd enable this settings at Windows 7. Intel offers USB 3.0 drivers for Windows 7, not for Windows 8. Therefore neither Intel supports USB boot. fix_USB3_SD.cmd adds Intel USB 3.0 settings at Windows 7. Windows XP doesn't support USB boot. XP USB boot is about 10 years old now: http://www.911cd.net/forums//index.php?showtopic=14181 Post #16 describes USB boot registry settings, e.g. [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\usbehci] "Start"=dword:00000000 "Group"="Boot Bus Extender" I've a Intel USB 3.0 series, Intel offers Version: 1.0.10.255 drivers. This won't support your hardware. https://downloadcenter.intel.com/download/21129/USB-3-0-Driver-Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-7-Series-C216-Chipset-Family I get at boot from Intel USB 3.0: BootDriverFlags and PollBootPartitionTimeout: Windows 7 does boot Start=0 : Windows 7 BSOD 0x7b It's experience about used local hardware. Can I recommend start=0? Increase boot time? Or combine start=0 and PollBootPartitionTimeout? http://reboot.pro/topic/14427-waitbt-for-usb-booting/

Which BSOD do you get? The BSOD indicates the next step 0x7E : driver version error 0x7B: timing erro, BIOS/UEFI behaviour influences this. As indicated previously, a timing issue could be resolved at Start=0 and group setting. I'll create another fix and test at local available hardware next weekend.

If you use x86 files, then you have to adjust the driver folder names. There won't be a folder sdbus.inf_amd64_* at x86 files. The command 'dir E:\mount\install\Windows\system32\DriverStore\sdbus* /s' lists available driver folder names. Mark, copy and paste the name. Windows 7 x86 works at CSM mode only. Windows 7 amd64 works at UEFI (secure boot disabled) and CSM mode. The suggestion was to try both: UEFI and CSM. eMCC may be handled differently at UEFI and CSM.

That's good, the drivers from Win7_USB3.0_Creator_v3 works fine at given hardware. Try again Windos 7 at USB hard disk. Similiar to previously approach, but use the drivers from Win7_USB3.0_Creator_v3

Use dirvers relating your ISO. Use x86 drivers, if you use a x86 OS. The log shows adding driver from FileResopitory. No, there are no drivers, add the subfolder name. Compare instructions again.

Follow the manual approach, just use the USB drivers from "Windows 7 USB 3.0 Creator Utility". With luck, these drivers works at Windows 7 booted from USB hard disk. Overwrite the lexar stick, no need for more so far. Sorry for the confusion. Yes, this is expected, igonre this so far, do not contine setup, press shift F10 instead. Remember small steps, this is the case: verify native SD drivers, searching a driver for the eMMC controller. If native SD drivers works, then it's time to create the next step.

Another game: native MMC and SD Windows 7 drivers There are native drivers at install.wim, but not at boot.wim. Transfer the files from install.wim to boot.wim first. And adjust registry settings, the previous fix_USB3_SD.cmd contains code already. As for testing small steps, start with a new boot.wim. Do not add USB3 drivers at first step. Add USB3 drivers later, if eMMC works by chance. Example, adjust used path yourself: USB stick with: U:\sources\boot.wim, U:\sources\install.wim Mount pathes C:\mount\boot and C:\mount\install dism.exe /Mount-WIM /WimFile:"U:\sources\install.wim" /index:2 /MountDir:"C:\mount\install" dism.exe /Mount-WIM /WimFile:"U:\sources\boot.wim" /index:2 /MountDir:"C:\mount\boot" dir C:\mount\install\Windows\system32\DriverStore\sdbus* /s dism.exe /image:"C:\mount\boot" /Add-Driver /driver:"C:\mount\install\Windows\system32\DriverStore\FileRepository\sdbus.inf_amd64_neutral_735aa3b5ee832f62" /ForceUnsigned dir C:\mount\install\Windows\system32\DriverStore\sff*.inf /s dir C:\mount\install\Windows\system32\DriverStore\FileRepository\sffdisk.inf_amd64_neutral_d2425e60845d17d3 dism.exe /image:"C:\mount\boot" /Add-Driver /driver:"C:\mount\install\Windows\system32\DriverStore\FileRepository\sffdisk.inf_amd64_neutral_d2425e60845d17d3" /ForceUnsigned dism.exe /image:"C:\mount\boot" /Get-Drivers /Format:Table fix_USB3_SD.cmd C:\mount\boot\Windows /SD_native_driver dism.exe /Unmount-wim /mountdir:"C:\mount\boot" /commit dism.exe /Unmount-wim /mountdir:"C:\mount\install" /discard Boot boot.wim. Does diskpart find the eMMC, are partitions available?