Jump to content

foobuzz

Members
  • Content Count

    44
  • Joined

About foobuzz

  • Rank
    Wanderer

Profile Information

  • Gender
    Male
  • Location
    Country of beer and pedantry
  • OS
    Windows 7 x64
  1. Hi RicaNeaga, The Information I got from a tech guy was wrong, usb controllers aren't from Renesas but from Intel. I've got the notebook system available now. Driver Magician, which I tried out first, shows me many components, but I guess all I need are pairs of an .inf and a .cat file (maybe .sys, too). I'm missing additional tools to get this more precise, though. Would you recommend the latest WT version, maybe a recent beta? Thanks for your help!
  2. Hi, I have to install W7 Ult x64 on a new DELL notebook systems that comes with W8 x64 and merely has USB 3 ports (i.e. no USB 2 port and no optical drive). I assume there might arise problems trying to install W7 SP1 x64 from a stick connected to a USB 3 port. I'm looking for an easy way to inject a Renesas USB 3 driver/driver family into the setup data (which file btw?). I make use of dism (mainly in scripts) or WinToolkit but am interested in the "recommended" method. Any ideas, suggestions, tips? Thanks in advance!
  3. Thanks Thiersee. Yes, I lost track a little bit with all the KBs... You're right, and obviously this is not related to my aforementioned "troubles". Greetings to Österreich!
  4. It gets better and better... Having done a real installation (not VM), after the updates mentioned above Windows Update came up with KB2533552. Just... why?!
  5. Addendum: Apart from 92. Change The Download Directory... everything seems to work fine! If only the langpack/WUA annoyance could be solved... P.S.: Just a thought, might be totally wrong: The WRP, should I disable it?
  6. I do not know what else to try, I feel really frustrated. :angry: I tried many many times to add English to my (german) Windows 7 Ultimate SP1 x64 build, but it simply doesn't work. It seems to get integrated (Updates tab) like all the other hotfixes and stuff, but doing a test installation in VM there is no additional language installed in Windows. I used both version 1.4.1.14 and the most recent 1.4.1.15. In the past with an older version I successfully managed to integrate the additional languages English and French, but I haven't stored the settings. (Btw, the file English_Win7SP1_x64.cab has been directly written with WT.) My current config: *AIO#ComponentsAppFrabicAustralia Local PackBranch CacheCanada Local PackClips In The LibraryCommon Modem DriversDelete 'Support' folderDelete 'Upgrade' folderDVD MakerGreat Britain Local PackHyper-V VMBUS DriverIIS Addons 1IIS Addons 2Inbox GamesInternet Explorer TroubleshootersInternet GamesMedia FeaturesMicrosoft AgentMicrosoft Storage ServiceMicrosoft XPS Document WriterMicrosoft-Hyper-V-GuestMusic and Video Examples (Ringtones)New Zealand Local PackOEM Help CustomizationParental ControlsPremium Inbox GamesPrint and Document ServicesPrinter DriversPrinting Premium Tools CollectionRIP ListenerShare Media Control PanelSound ThemesTablet PC ComponentsTelnet ServerTFTP ClientWindows Anytime UpgradeWindows Anytime Upgrade ResultsWindows Media CenterWindows Media PlayerWindows Media Player DVD RegistrationWindows Media Player Network Sharing ServiceWindows Media Player TroubleshootersWindows TIFF IFilterXPS Viewer#DriversC:\Updates\Drivers\Atheros Ethernet\L1c62x64.inf#ServicesBranch Cache::DisabledFax::DisabledParental Controls::DisabledSmart Card::DisabledSmart Card Removal Policy::DisabledWindows Defender::DisabledWindows Error Reporting::DisabledWindows Media Center Receiver::DisabledWindows Media Center Scheduler::DisabledWindows Media Player Network Sharing::Disabled#Silent InstallsKB2533552::N/A (Not Needed);NO;9.23 MB;C:\Updates\Optional\Windows6.1-KB2533552-x64.msu;Always Installed#TweaksAdd 'Unpack' to *.msi context menuRemove 'Add to WMP list' from Audio context-menuRemove 'Print' from context-menuAdd 'Register' and 'Unregister' to *.dll, *.ocx and *.ax Context Menu500ms Delay Aero PeekDisable Recycle BinHide Recycle BinRemove the Action Center iconAllow 3rd Party ThemesAlways Show Menu BarsAutomatically Expand to Current FolderControl Panel View::Large IconsDisable Last File Access TimestampDisable Search Online on Unknown File ExtensionsDisable Shortcut Link ResolveDisable Thumbnail CacheLaunch Folder Windows in a Separate ProcessRemove 'HomeGroup' from ExplorerRemove 'Libraries' from ExplorerRemove Shortcut ArrowRemove Shortcut SuffixShow Drive Letters FirstShow Explorer StatusbarShow File ExtensionsShow Hidden Files & FoldersSpeed Up DesktopSpeed-up Access to AVI Media FilesEnable SSL and TLSAlways Show Menu BarChange The Download Directory::C:\interimDisable Default Browser CheckDisable Signature checking for EXEsDisable Warning on Close (Tabs)Enable 'Caret' BrowsingEnable Saving Encrypted Pages to DiskEnable Third Party ComponentsFaster Browsing in IE Launch Internet Explorer in Separate ProcessRemove Links BarUnlimited Simultaneous DownloadsConnect To::HideControl Panel::LinkDefault Programs::HideDevices and Printers::HideDocuments::HideDownloads::HideFavorites::HideGames::HideHelp and Support::HideHomegroup::HideMusic::HidePersonal::LinkPictures::HideRecent Docs::ShowRecorded TV::HideRun::ShowVideos::HideEnable context menus and dragging and dropping::EnableDisable Startup soundShutdown QuickerAlways Unload DLLBlock Negative DNS EntriesDisable Admin SharesDisable Automatic Restart on BSODDisable Dr WatsonDisable Mapped Drive Checking on Startup::Disable CheckingDisable SuperfetchDisable Window 7 built-in CD/DVD BurningDisable Windows Error ReportingDon’t allow Windows to turn off devicesIncrease RPC Packet SizeKeep Positive DNS EntriesTurn off system beeps#vLiteEase of Access ThemesExtra Themes#UpdatesC:\Updates\WUA\WUClient-SelfUpdate-ActiveX.cabC:\Updates\WUA\WUClient-SelfUpdate-Aux-TopLevel.cabC:\Updates\WUA\WUClient-SelfUpdate-Core-TopLevel.cabC:\Updates\Langpacks\English_Win7SP1_x64.cabC:\Updates\IE10\Windows6.1-KB2670838-x64.msuC:\Updates\IE10\IE10-Windows6.1-x64-de-de.exeC:\Updates\IE10\IE10-Windows6.1-KB2792100-x64.msuC:\Updates\IE10\Windows6.1-KB2729094-v2-x64.msuC:\Updates\IE10\IE10-Windows6.1-KB2797052-x64.msuC:\Updates\.NET\Windows6.1-KB2656356-x64.msuC:\Updates\.NET\Windows6.1-KB2604115-x64.msuC:\Updates\.NET\Windows6.1-KB2656411-x64.msuC:\Updates\.NET\Windows6.1-KB2736422-x64.msuC:\Updates\.NET\Windows6.1-KB2729452-x64.msuC:\Updates\.NET\Windows6.1-KB2756921-x64.msuC:\Updates\.NET\Windows6.1-KB2742599-x64.msuC:\Updates\.NET\Windows6.1-KB2789645-x64.msuC:\Updates\Optional\Windows6.1-KB2506014-x64.msuC:\Updates\Optional\Windows6.1-KB2515325-x64.msuC:\Updates\Optional\Windows6.1-KB2552343-x64.msuC:\Updates\Optional\Windows6.1-KB2708075-x64.msuC:\Updates\Optional\Windows6.1-KB2718704-x64.msuC:\Updates\Optional\Windows6.1-KB2709981-v2-x64.msuC:\Updates\Optional\Windows6.1-KB2699779-v2-x64.msuC:\Updates\Optional\Windows6.1-KB2661254-x64.msuC:\Updates\Optional\Windows6.1-KB2735855-x64.msuC:\Updates\Optional\Windows6.1-KB2749655-x64.msuC:\Updates\Optional\Windows6.1-KB2739159-x64.msuC:\Updates\Optional\Windows6.1-KB2732500-v2-x64.msuC:\Updates\Optional\Windows6.1-KB2732487-v2-x64.msuC:\Updates\Optional\Windows6.1-KB2646886-v2-x64.msuC:\Updates\Optional\Windows6.1-KB2762895-x64.msuC:\Updates\Optional\Windows6.1-KB2685811-x64.msuC:\Updates\Optional\Windows6.1-KB2685813-x64.msuC:\Updates\Optional\Windows6.1-KB2779272-x64.msuC:\Updates\Optional\Windows6.1-KB2786081-x64.msuC:\Updates\Optional\Windows6.1-KB2726535-x64.msuC:\Updates\Optional\Windows6.1-KB2760730-v2-x64.msuC:\Updates\Optional\Windows6.1-KB2794119-x64.msuC:\Updates\Security\Windows6.1-KB2476490-x64.msuC:\Updates\Security\Windows6.1-KB2479943-x64.msuC:\Updates\Security\Windows6.1-KB2491683-x64.msuC:\Updates\Security\Windows6.1-KB2503658-x64.msuC:\Updates\Security\Windows6.1-KB2506212-x64.msuC:\Updates\Security\Windows6.1-KB2509553-x64.msuC:\Updates\Security\Windows6.1-KB2511455-x64.msuC:\Updates\Security\Windows6.1-KB2524375-x64.msuC:\Updates\Security\Windows6.1-KB2532531-x64.msuC:\Updates\Security\Windows6.1-KB2536275-x64.msuC:\Updates\Security\Windows6.1-KB2536276-v2-x64.msuC:\Updates\Security\Windows6.1-KB2544893-x64.msuC:\Updates\Security\Windows6.1-KB2560656-x64.msuC:\Updates\Security\Windows6.1-KB2564958-x64.msuC:\Updates\Security\Windows6.1-KB2570947-x64.msuC:\Updates\Security\Windows6.1-KB2579686-x64.msuC:\Updates\Security\Windows6.1-KB2584146-x64.msuC:\Updates\Security\Windows6.1-KB2585542-x64.msuC:\Updates\Security\Windows6.1-KB2618451-x64.msuC:\Updates\Security\Windows6.1-KB2619339-x64.msuC:\Updates\Security\Windows6.1-KB2620704-x64.msuC:\Updates\Security\Windows6.1-KB2620712-x64.msuC:\Updates\Security\Windows6.1-KB2621440-x64.msuC:\Updates\Security\Windows6.1-KB2631813-x64.msuC:\Updates\Security\Windows6.1-KB2644615-x64.msuC:\Updates\Security\Windows6.1-KB2645640-x64.msuC:\Updates\Security\Windows6.1-KB2653956-x64.msuC:\Updates\Security\Windows6.1-KB2654428-x64.msuC:\Updates\Security\Windows6.1-KB2655992-x64.msuC:\Updates\Security\Windows6.1-KB2658846-x64.msuC:\Updates\Security\Windows6.1-KB2659262-x64.msuC:\Updates\Security\Windows6.1-KB2660649-x64.msuC:\Updates\Security\Windows6.1-KB2667402-v2-x64.msuC:\Updates\Security\Windows6.1-KB2685939-x64.msuC:\Updates\Security\Windows6.1-KB2690533-x64.msuC:\Updates\Security\Windows6.1-KB2691442-x64.msuC:\Updates\Security\Windows6.1-KB2698365-x64.msuC:\Updates\Security\Windows6.1-KB2705219-v2-x64.msuC:\Updates\Security\Windows6.1-KB2712808-x64.msuC:\Updates\Security\Windows6.1-KB2716513-x64.msuC:\Updates\Security\Windows6.1-KB2719033-x64.msuC:\Updates\Security\Windows6.1-KB2724197-x64.msuC:\Updates\Security\Windows6.1-KB2727528-x64.msuC:\Updates\Security\Windows6.1-KB2736233-x64.msuC:\Updates\Security\Windows6.1-KB2743555-x64.msuC:\Updates\Security\Windows6.1-KB2753842-v2-x64.msuC:\Updates\Security\Windows6.1-KB2757638-x64.msuC:\Updates\Security\Windows6.1-KB2758857-x64.msuC:\Updates\Security\Windows6.1-KB2769369-x64.msuC:\Updates\Security\Windows6.1-KB2770660-x64.msuC:\Updates\Security\Windows6.1-KB2778344-x64.msuC:\Updates\Security\Windows6.1-KB2785220-x64.msuC:\Updates\Security\Windows6.1-KB2790113-x64.msuC:\Updates\Security\Windows6.1-KB2790655-x64.msuC:\Updates\Security\Windows6.1-KB2799494-x64.msu#OptionsCompatibility CheckCreate BackupsEnable BeepForce UnsignedIntegrate 'HDC' Drivers (boot.wim)Integrate 'SCSIADAPTER' Drivers (boot.wim)Integrate 'SYSTEM' Drivers (boot.wim)Prepare DriversPrompt AddonsPrompt DriversPrompt GadgetsPrompt SilentPrompt ThemesPrompt UpdatesPrompt WallpapersRebuild ImageShow Duplicates After activating Windows Updates in the test installation and retrieving the important update list I'll get 2 matches: 1 EU cr*p and 1 obsolete KB2676562 hotfix. Usually I disable them. As the English localisation isn't available, I picked it out of the Optional update list and installed it online. Next strange thing: Having done that (verified in Control Panel, Regions...), WU nags me to re-install the (already integrated and installed) WUClient and having done that it will suggest me all important february patchday 2013 items (even though they have been integrated)! What the heck's going wrong here?! This is driving me nuts...
  7. So "mctadmin" seems to be "safe to delete", all right. Thank you, sp0iledbrat. Edit: Just decided to keep it, it doesn't seem to interfere with my oem stuff any more.
  8. Just found out that WT 1.4.1.14 seems to set a registry entry at [HKEY_USERS\TempHive\Software\Microsoft\Windows\CurrentVersion\RunOnce] "mctadmin"="C:\\Windows\\System32\\mctadmin.exe" (In this sample TempHive is an imported NTUSER.DAT structure) I assume it stems from an option in the Tweaks section of the AIO-Integrator, just which one? I try to write a registry setting for this registry key (accessing the TempHive structure) via RunOnceEx and before the (new?) entry mctadmin appeared that worked fine, now it doesn't any longer. I tried with this line Reg add %K%\010 /f /v 4 /d "reg delete HKU\TempHive\Software\Microsoft\Windows\CurrentVersion\Runonce /f /v mctadmin" to delete it before writing my own value, however this didn't work out. :g:
  9. First off, I noticed that not even Microsoft has a clue. Just codswallop in TechNet and elsewhere... I'm also encountering this warning (VM only, not on a "real" system). I tried the following: Launching the service Microsoft .NET Framework NGEN v2.0.50277_X86 (state: manual, not started), then rebooting Windows 7. It'll be inactive again and no new warning should have been generated.
  10. Do you mean Restore Default Theme? It won't make a difference. I'll have "classic" view (basic design, high contrast) selected anyway... P.S.: Doesn't work with Force Aero (registry?) tweak either! Always basic from the beginning...
  11. I'm not sure, but it seems I recently had the same bug with version 1.4.1.14... I took the All-In-One Integrator and removed "Ease of Access Themes" and "Extra Themes". I did an installation featuring a self made Autounattend.xml (which also sets Aero). Apparently, c:\Windows\Resources\Themes\aero.theme and c:\Windows\Resources\Themes\Aero\*.* don't suffice... ?! So Windows' Classic Style is activated instead of Aero. Why do I have to keep the damn Ease of Access stuff just to ensure Aero?
  12. Seems I cannot access your file, AdF.ly stopped working (using Firefox/Chrome). What's the benefit of your repacked release?
  13. Thank you for clarifying this! Just thought that it should be possible to have KB2533552 alone, but obviously that's not the case.
  14. Another question: Which W7 version did you use (SP1, yes or no)? On the last screenshot I see update KB976902 which is a pre-SP1 system update as Thiersee already stated. Strange that I found it in a freshly installed W7 SP1 -- it can't be removed later by running wusa.exe /uninstall /kb:976902 The date of this update goes back to the year 2010, so I doubt it's part of SP1 (date stamp: mid 2011). Personally, I see no use for it in a current W7 build. Where does it come from? And how may I prevent its integration?
  15. Well, I don't like this software either, but as I can't refrain from it (it's necessary for some M$ downloads), I want to have the latest version available. That's all, the relevant tasks will be done with Firefox or Chromium (i.e. real browsers). Back to topic: I've seen (english and localised) .exes and .cabs so far. There also seems to be 4 Updates for Windows needed for a newly installed Windows 7 SP1 (x64) prior to launch IE10's setup. The fascinating question is: How can I inject the preview (and its dependending updates) into the install.wim? Are there any ideas, suggestions, scripts?
×
×
  • Create New...