Hmm, okay. Thanks Speaking of which, when I was slipstreaming updatepacks in XP, I found out that the .NET Framework installers require a live install, making slipstreaming impossible. However, unless I am mistaking, the Windows 7 installation disc consists of a (pretty much) finished live install that is packed into one large file. So I am wondering, why isn't it possible to slipstream .NET Framework in 7?
There is certainly some reason we don't know about. There are also several regular hotfixes/updates that cannot be integrated. Even if they are slipstreamed as addons or silent installers, they are still not truly integrated, only added to install before first logon (invisibly or not). The only "real" integration is by using Sysprep.
What does •Tweek registry instead of MRT ( KB890830 ) mean? Is MRT integrated or is there some registry tweak that prevents MRT to show on Windows Update?
Registry tweak suppose to add fake information that MRT is installed, but In reality it is not. It refers to particular monthly MRT (Microsoft Windows Malicious Software Removal Tool) update.
Is this a good decision? So every now and then there is new MRT and will this new MRT be shown on Windows Update or this tweak completely disables MRT?
New MRT will be shown next month during regular Windows update PS MRT is not very useful and effective against viruses/malware having in mind that everyone has some Anti-virus program on computer. Also, its process runs in background and slows the machine
gamazet thank you for the update package you have put together. I have been searching for this type of bundle that can update my base Windows 7 and Windows 2008R2 ISO images using a WISM.exe and a few switches. The name Simplix Pack says it all. Hope to see a Simplix Pack for Win8/Win2012 in the near future.. Happy New Year Greetings! Keep up the good work!
Simplix is the nick name of the creator. Happy Holidays and New Year to you also, and to all other members
Thanks for enlightening me on how this update package came to be known as Simplix I just started using the updater and ran into a small problem, hope you can help me here. I ran the updater and tried to stop it by doing CTRL-C. What this has done now is each time I launch the Updater I am getting a message "Update Installer is already running please wait" . I have rebooted the machine but still keep getting the same message. I checked for any background process running but could not find anything obvious. What could be causing this?
I am not sure. But could try the following: Right click on the Computer icon and select Manage - than click on "Services" (or on start menu - search - type services). Select Services, right click on Windows Installer in the list and select Properties. In the Properties dialog, change Startup type to “Disabled”, click OK, and reboot your computer. This should stop the service. After your computer reboots, again open Computer Management (right click on Computer and select Manage), open Windows Installer Properties, and change the Startup type back to Manual.
I tried setting the Windows Installer and Windows Update services to disabled - rebooted but still same problem. I moved the updater to my Windows 7 x86 machine and it seems to run fine, but when I run it on my x64 Windows 7 machine I am getting this message. I suppose I can use my x86 machine to update the iso images, I just thought I use the x64 machine which has more horsepower and ssd drive to speed up the updating process. I will keep persevering to see if I can get it to work and report back my findings for others to know should they run into a similar issue. Thanks!
Code: File: UpdatePack7Live-13.12.15.exe CRC-32: f5b2bf42 MD4: 345f1f364de25400bc9797e3e9ad858e MD5: 5ef00589221216b551297de7e5ba8fc9 SHA-1: dff01c1b2e2cbebec789a66917284ebd6c5a0db5
This pack seems to be the best one. I've tested a few and also tried WUD & WHD but they aren't tested against prerequisites and so on. I really like it and will use it as my w81 project failed (caused by microsoft and unstable drivers)
Based on Win7Prox64SP1 Media Refresh and UpdatePack7Live-13.12.15.exe There are some updates included that are superseded. It's nothing to really worry but maybe he can flush them with the next release. From the DeepClean.log Code: Total size of superseded packages: 139.89 MB (146,685,382 bytes) Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 superseded - uninstalled Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514 superseded - uninstalled Package_for_KB2532531~31bf3856ad364e35~amd64~~6.1.1.0 superseded - uninstalled Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0 superseded - uninstalled Package_for_KB2653956~31bf3856ad364e35~amd64~~6.1.1.5 superseded - uninstalled Package_for_KB2655992~31bf3856ad364e35~amd64~~6.1.1.3 superseded - uninstalled Package_for_KB2656356~31bf3856ad364e35~amd64~~6.1.1.1 superseded - uninstalled Package_for_KB2691442~31bf3856ad364e35~amd64~~6.1.1.3 superseded - uninstalled Package_for_KB2706045~31bf3856ad364e35~amd64~~6.1.1.0 superseded - uninstalled Package_for_KB2758857~31bf3856ad364e35~amd64~~6.1.1.0 superseded - uninstalled Package_for_KB2785220~31bf3856ad364e35~amd64~~6.1.1.0 superseded - uninstalled Package_for_KB2834140~31bf3856ad364e35~amd64~~6.1.1.1 superseded - uninstalled Package_for_KB2836942~31bf3856ad364e35~amd64~~6.1.1.0 superseded - uninstalled Package_for_KB2855844~31bf3856ad364e35~amd64~~6.1.1.2 superseded - uninstalled DC: Scavenging files using CBS API...