Code: mount the boot.wim index:2 dism.exe /image:"x:\mount" /Add-Driver /driver:"y:\USB3x_7" /recurse save and unmount boot.wim y:\USB3x_7 being the path to and folder, containing the USB3.x drivers.
If the live-USB flash drive is booting up now in the new Notebook which has only USB 3.0 controller and ports, could this still be the issue? Not sure if you saw my Edit above where I'm back to the CD/DVD drive device driver missing error message.
I recently watched a friend using this updatepack on an installed system which took ages to finish with restart after restart. will it be efficient if integrated into windows iso before installation? or it will take as much time as a post installation update?
It is quicker if integrated but you must also include the time it takes to integrate the hotfixes if one time installation i would just install pack after windows installation but if you are going to use on multiple machines then integrate. Another thing is the spec of the machines that can depend on how long it takes. But still far quicker than windows update. And make sure you read first page i,e, Switches .
That depends on the current condition of said live system. If you fresh-install a clean MSDN image and then run the updatepack on that, yes, it will take... "ages" and the updates will be installed in groups with multiple restarts between said groups. If you're just updating a fairly up-to-date system, the updatepack is gonna need to install only a few(maybe less than 15-10) updates and that does NOT take "ages" to complete. If a clean install of windows is needed anyway, it's way better to use the pack to update an image offline and then use the updated image for the clean installation. Personally, I've rarely used the pack as a live update tool. I've always prepped images for people's machines, then gave them the iso plus a .zip with the drivers that weren't integrated and tell them to keep those safe for future use.
I was also wondering how much time it would take on a fresh install of w7 sp1. So far, I install the convinience rollup (kb3125574), plus the update needs to be installed beforehand (kb3020396) and I let windows update do the rest. Making a new image every time an update is out is no go for me.
You service an image once > you install it > you run the every month's updatepack and install 1-10 updates > profit
Unfortunately,19.6.15 digital sign is unable to verify,19.4.10 and 19.5.15 are direct revoking for me.
No issues here with the sums. I used the magnet link to download the file Code: $ md5sum UpdatePack7R2-19.6.15.exe 8c53e003f5068fb201e25ec9c5ebd31d UpdatePack7R2-19.6.15.exe $ sha1sum UpdatePack7R2-19.6.15.exe 5eb7aba8cbdc3816b044269c20eb4eeb9bfee5e0 UpdatePack7R2-19.6.15.exe
Thanks for this... I just read the Whole Thread, what an Cluster*uck it is... Lets hope all works out and idealy he get his cert back or at least get compensated.. Cheers