New update with 'No public hotfixes' message on request sheet: KB2616386: Windows Explorer displays wrong access control entries for migrated user accounts in Windows 7 or in Windows Server 2008 R2 Sechost.dll 6.1.7601.17690 Sechost.dll 6.1.7601.21817 Advapi32.dll 6.1.7601.17690 Advapi32.dll 6.1.7601.21817
Ok but why then burfadel's script installs both GDR and LDR binaries - just to satisfy WU?!? From what I understand, if GDR binary installed, the next update will install GDR-only file(s). On the contrary, if the binary is applied an LDR-only hotfix, the subsequent update will install LDR file(s). But what I don't understand is why then there is a need to install both branches (GDR + LDR) on a computer using burfadel's script?!? Sorry for going back to the same topic again and again but I'm still not satisfied by replies... No pun intended but either I don't understand the mechanics behind Windows updates, or there is a contradiction which needs detailed explanation... Thanks for understanding!!!
I have had some horrendous results with Win7 default drivers (on a stable system with well-matched components). Including BSOD due to unfit NIC drivers, display crashes due to Win7 default graphics drivers, altogether horrendous performance due to outdated Chipset drivers. So yes, you need to get the latest or appropriate drivers for your system. This is why, if you re-install Windows but had the factory install before that, you need to backup the functional drivers you had via a free app called "Driver Magician Lite" or something similar. Then you save those backed up drivers somewhere, and use them to install your hardware on your new Win7 install. Otherwise, use a diagnostic tool like Speccy or HWINFO (both free) to determine your hardware brand and model, and download the drivers from the manufacturers, etc.
I'm trying to modify burfadel's script (sorry) to my own requirements and I have trouble understanding this line, as a matter of fact, it won't even read. im GUESSING its possibly because i changed the temp folder path, and the format of the following line depends a lot on %temp%. I would like clarification for /f "tokens=8-9 delims=\ " %%a IN ('dir /b /on "update*.mum" /s /b') DO (set file=%%a\%%b&call :listcreate) What's the expected output of %%a and %%b as an example?
Another thing to check: by default, write caching is turned off for USB connected drives (to help prevent data loss). If you want the fastest transfer speed, you'll want to turn it on. The caveat for doing this is that you'll need to click the "Safely Remove Hardware" icon before disconnecting the drive. To enable write caching, go into Device Manager->Disk Drives and find your device. Rt-click it, select the Policies tab, choose "Better Performance", then OK. For more info on this, look in the middle of this page where it says "enable write caching": hxxp://support.microsoft.com/kb/2442580
The tokens=8-9 refers to the location of the contents of the cabtemp folder, the delims=\ adding one extra 'token', such that tokens 8-9 refers to the extracted path of the update in relation to the base cabtemp folder. The %%a\%%b refers to the 8th and 9th tokens from tokens 8-9. If you change the temp folder, you need to change the tokens to reflect this.
Yeah I figured that out after copy pasting %temp% folder path... to study it haha. Through your script, I think I've finally understood for loops.
burfadel: does your script actually install subfolders? such as IE9, LDR placeholder? I look at your 21b script and it doesn't seem to do anything like that. Any reason for that?
Continuity mainly, but also because of the necessity of the files in the subfolders. For most people, these files aren't applicable, and in the cases where specific updates are applicable they can be copied to the main folder after testing their applicability by running (but not installing) the update... or at least thats the intention of the script. Using cab option 3, if you continually find updates that are trying to be installed but aren't, its because they aren't applicable either because of the wrong service build, is older than the update currently installed, or is for a non-present feature. There are a couple of updates that will always try and install but aren't applicable, and won't actually instal as they are RTM updates, but these aren't present in SoLoR's repository.
Yeah, the idea was to have those updates which are applicable from the subfolders copied to the main folder. Most of those updates for the majority of people aren't applicable, it seemed kind of pointless doing the preparation and having DISM try. Any automation of updates of any kind, regardless of whether its my script, any other script, program, or post setup auto installation etc, requires the user to know what they are installing and that they are relevant. This includes superseded updates (not including LDR placeholders), updates for the wrong service branch (RTM, SP1 etc), updates that aren't applicable etc.
A bunch of new Office 2010 updates are now out: Outlook-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596485 Word-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596551 Access-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596496 Project-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596495 Visio-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596553 Mso-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596501 Gfx-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596552 Ace-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596587 Oart-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596500 Pptview-x-none.msp & Powerpoint-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596503 Excel-x-none.msp & Graph-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596554 Onenote-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596589 <-not currently in repository, but probably should be added Vbe7-x-none.msp 14.0.6112.5000 hxxp://support.microsoft.com/kb/2596585 <-not currently in repository