Jump to content

Mark7ones

Member
  • Content Count

    18
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by Mark7ones

  1. Setup: 1) Working driver: [xHC_wdfsect] KmdfLibraryVersion = 1.9 2) Not working driver (downloaded from Gigabyte): [xHC_wdfsect] KmdfLibraryVersion = 1.11 The second driver is for Windows 8, also compatible with Windows 7 but not usable during setup. Of course I did not know...
  2. I don't know... according to the date in the .inf file, the driver I have integrated is more recent. But I still do not understand why the drivers I use for the system. for the same controller. are not good for setup.
  3. Solved. I have slipstreamed the drivers from this pack: https://pcorakel.stackstorage.com/s/TZ47bLjfLs2M9wv. These VIA drivers work, the ones I downloaded from Gigabyte no.
  4. Right, my VIA controller has two drivers (ViaHub3.inf and xhcdrv.inf) integrated in both boot.wim images (winpe and setup) and install.wim. There's something I cannot understand, because even if I load drivers manually it doesn't work...
  5. Ok, so basically, as suggested by cdob, you have to edit the registry in offline mode. Jaclaz, have you tested the batch he posted or should I check it?
  6. Sorry ... I'm sure I've integrated the right drivers (VIA_XHCI_Driver_V4.90A_AP). I'm not really a newbie. Also, I tried on a different pc with all the USB 3.0 drivers available (Etron, AMD). The problem is not the drivers, the problem is Microsoft. I'll read that thread, let's see if there's anything interesting...
  7. Did anyone succeed to install Windows 7 from USB 3.0? Because I have integrated the drivers in boot.wim and install.wim, but I always get the same error (missing driver). I also tried to load them from a folder or to install in UEFI mode ... no way! It's quite frustrating...
  8. Sorry for the late... It's been years I don't use RT7Lite or vLite, but WinReducer is still full of bugs and DISM is a nightmare. So, for the guys, like me, who will never upgrade to W10, this is the tip of the year... You're installations have crashed not for this or that component... but simply because you removed the screensavers... lol Just a little bug from RT7Lite... For those who still use vLite, well I don't have any problem (even if this app is for Vista). It's fairly simple, you have less things to remove and it works well when it has to clean WinSxS fol
  9. Ok I did some tests, as I did some months ago (this is not the first time I try to use this tool). So here are the conclusions: -It DOES NOT remove anything in OFFLINE MODE. -Use DISM instead (after you have unhided the packages) or use the tool in ONLINE mode. -These packages (removed with DISM) break Windows Setup: Windows Client Language Pack Windows Client Drivers Windows Common Drivers -Internet Explorer package removal breaks MMC (you can remove optional and troubleshooter packages). -Some packages cannot be removed in DISM (error 0x800F0805),
  10. Hi guys, Does this tool remove registry keys or packages? Because, I still see the removed packges (/c /r) inside the image. I did the same question 8 months ago... no answer. So let's do some spam. Does this tool remove registry keys or packages? How does it work? Does it work? No errors and no packages removed. No errors and no packages removed. No errors and no packages removed. No tv and no beer make Homer go crazy. No tv and no beer make Homer go crazy. No tv and no beer make Homer go crazy. It works only
  11. Anyone knows why this tool says it removed the packages but actually it didn't remove anything? I'm trying to remove some stuff from Windows 7 x64 in offline mode; I didn't get any error message, but the image size is identical and if I install the system the packages are still present. I also tried the latest version, no way.
  12. It didn't work even without IE10 integration. Making unattended installation with Microsoft is a nightmare. There's a problem for every pass... For example, I wanted to disable some features or packages and it didn't work. Now I know that I have to apply unattend.xml to install.wim to make it works. For updates it seems unattend switch (Sysprep) is required... What can I say? Microsoft f**k off!
  13. It didn't work because I changed this value in registry: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "SeparateProcess"=dword:00000000 Don't set to 1 (leave default).
  14. As many of you know, Theme Resource Changer is a utility that allows to change Windows Explorer icons (e.g. Navigation buttons), without replacing .dll files. Now it seems that sometimes this program fails to work (I still have default icons even after patched Windows with all apps I can find: Universal Theme Patcher, UltraUXThemePatcher, UxStyle_Core_Jul13_x64). Did anyone find a solution?
  15. I had successfully installed Win7 from usbdrive using Autounattend.xml file and installed Win7 with integrated updates following standard procedure. If I try to deploy unattended installation of a Windows copy with integrated updates I get this error. It seems like Windows cannot handle integrated updates in unattended mode. Maybe some istruction in xml file's needed. Autounattend.xml
×
×
  • Create New...