guys, any solution I got this error : View attachment 26765 failed to install the update, access denied. therefor I interrupt it because it will waste my time to wait the process with no result. what I do : put WIM file in drive C ( extracted from win7 ultimate untouched media refresh ISO ) put update in drive C run command UpdatePack7Live.exe /ie11 /WimFile=C:\install.wim /Index=* as administrator *sorry for my bad English I hope you understand what I mean.
In that case command should be UpdatePack7Live.exe(or UpdatePack7Live-14.1.20.exe) /ie11 /WimFile=C:\WIM\install.wim /Index=*
updated!!! Наборы - UpdatePack7 Live версия 14.2.15 lСкачать (размер 457 МБ) | rghost | mega | rutracker BitTorrent Sync: RFNZNAHV4KL5Q7CBVTQTKQ3HU6NDUOKSZ Используя BTSync вы будете получать новые версии автоматически MD5: 955817b6ff8a647d77ed3d87a256ac11 *UpdatePack7Live-14.2.15.exe Список обновлений и история изменений thanks, gamezet, simplix!
Change the working folder path Nice solution, very nice indeed. However it would be great to add the feature to be able to change the working folder path, see I use to work on a secondary HDD with letter S: assigned, but this tool works by default on C: and such thing is not good for me due the lack of space.
What do you mean, when updating windows or integrating updates? When integrating updates simply change drive, for example: Code: UpdatePack7Live.exe /ie10 /WimFile=S:\install.wim /Index=*
Yes, I mean the latter. Actually that's the same syntax I use but the program needs to work on C drive.
It's seems that program is looking for system drive where DISM and other system files are installed (C:\ is default)
I can understand this, however the working folder where decompressing updates and dism operations could be set on any other location or path at user convenience. This feature would be very useful and In the meantime I workaround lack of space in C: by re-sizing partitions a bit. Finally, I could add that this Simplix's solution is working flawless, thank you very much to you and to the creator.
What do you mean override? Maybe, supersedes? If so, that's because old updates, hotfixes, etc. are obsolete, then new ones come up and supersede them. That's why you see new ones and old ones gone within updated Simplix packs.
Hi gamazet. Thank you so much for your work in this Simplix pack! I have been maintaining my own "fully updated" slipstream project over the years, but this pack seems to so professionally done and regularly updated that I think I will transition to just using it. One feature request: I would like to see the update pack configure the installation source so that KB2533552 is installed on the first boot, since it cannot be integrated. For example, I've been doing the following on my personal build ever since KB2533552 was released back in 2011: Code: rem use dism to mount install.wim mkdir C:\mount dism /mount-wim /wimfile:D:\Applications\OS\Windows\7\3-PreHotfixIntegration\5-Slipstream\PreHotfixIntegration\sources\install.wim /index:1 /mountdir:C:\mount rem hotfix KB2533552 cannot be integrated, so automatically install it on first boot mkdir C:\mount\Windows\Setup\Scripts copy D:\Applications\OS\Windows\7\3-PreHotfixIntegration\4-KB2533552\SetupComplete.cmd C:\mount\Windows\Setup\Scripts\ copy D:\Applications\OS\Windows\7\3-PreHotfixIntegration\4-KB2533552\Windows6.1-KB2533552-x64.msu C:\mount\Windows\Setup\Scripts\ rem commit changes dism /unmount-wim /mountdir:C:\mount /commit del /q C:\mount "Windows6.1-KB2533552-x64.msu" is obviously the installer for KB2533552 on Windows 7 64-bit. "SetupComplete.cmd" is the following: Code: %WINDIR%\Setup\Scripts\Windows6.1-KB2533552-x64.msu /quiet /norestart del %WINDIR%\Setup\Scripts\Windows6.1-KB2533552-x64.msu del %WINDIR%\Setup\Scripts\SetupComplete.cmd del /q %WINDIR%\Setup\Scripts\ Is this possible integrate/emulate this functionality into the update pack? Thanks again for your awesome contribution to the Windows 7 community.
Zamiell, Your thanks goes to Simplix! Your script is interesting and will certainly be of use for many others here on MDL. But not only KB2533552 cannot be integrated, there are also 4-5 other hotfixes that must be installed with run-once or with script like yours or other method. I don't know why but it seems that Simplix is not too much worried about that. I think he doesn't want to imply solution to users, but he is leaving it to their choice
Hi... Very wonderful project, Thanks. I think it would be nice if KB2775511 also added to the package. Well it's not displayed when checking for updates in Microsoft/Windows Update, but anyway I think we would have a more complete pack after adding KB2775511. Any idea?