Stimpy

Strange, just done another integration, and forgot to put KB2777294 in to the silent instal list, and this time it integrated just fine... Hmmmm

Well adding KB2777294 to the silent instal list seems to have fixed the problem. I have just checked it in the VM and it says it's installed. So Lego, you need to make a new rule for this hotfix in your next build. :cap:

Hi all, I'm just making a new image, and just had it fail on KB2777294 64bit version. Any ideas? Oh, and please don't worry about the source folder saying it's x86, it is the 64Bit version inside! KB2777294x64.txt

It would be cool if the ToolKit also could download the WU_Satisfy folder as well. (Win8)

It's a program called Windows Download Integrator, but I have never been able to download it, because the creator of this program removes the download links when he has found a bug, then spends weeks fixing it, then says stuff like "will be released in a week", this was said at the beginning of this month, and still nobody has no idea when/if he's going to release it, BUT he could be waiting for McRip to finish re-opening his servers, maybe. UPDATE: He has now released a Beta version, and is available HERE

McRip will be re-opening his servers in a few days. Win7 and office first, then a few days later Win8 should follow. UPDATE: McRip has got the Win7 Repo back online now. It is only accessible through WinToolKit, and one other program.

His blog has never been offline, however up until very recently, all links from the blog were being re-directed to Microsoft's site, or a nice picture of a girl walking away, giving us the finger...

It is uncanny how this is ending up being the same as Solor, I don't really understand it myself. However I do know that there are a lot of asshats out there that demand too much from McRip, and are pretty damn rude about it, usually non-english speakers I'm afraid. (but not in all cases!) I guess we will have to wait and see what happens. But yeah, McRip seems openly quite hostile towards everyone now. I just hope he at least says what he decides, rather than pulling a Solor.

Hi Lego, Yeah, it mounts perfectly... No warnings. It then opens the WinToolKit_Mount Folder, and the contents of it look correct. It also unmounts correctly, with no warnings/errors. The problem seems to be when you try to use the ISO Maker (by pressing the Make ISO button in the WIM Manager), as all it does is create an ISO that contains the WIM file (not decompressed). Also the ISO Maker is not pre-populated with the file/folder location information. Is this intended behaviour, as I have never used the WIM Manager before?

You really annoy me. You come across rude and arrogant. I would like to know where it explicitly stated that the WIM Manager does not work on ALL WIM files? Making me out to be some kind of idiot just makes you unwanted here. This community is about helping each other, not laughing and pointing fingers at those that don't know every function of this program. It's not like I was trying to use Logitech Setpoint to program the guidance system of a rocket!

McRips server is down, so nothing Lego can do about it.

I think we mis-understand each other. My problem is that I tried to use the WIM Manager part of WinToolKit to make modifications to a WinPE.WIM that comes as part of the Windows 8 Assessment & Deployment Kit. I did not know that the WIM Manager function of the ToolKit does not work with anything other than those WIM files that contain a full Windows OS. I was simply thinking that the ToolKit was going to be a nice and easy short-cut for helping me make modifications to the WinPE.WIM file, (mount the WIM, make some modifications, save the WIM, then make an ISO out of it for PXE booting, functions that I thought the WIM Manager performed) and that's when I thought that I had found a problem with the Toolkit. Now it seems to me that WIM Manager is not actually meant for use with ALL WIM files, only those that contain a full Operating System, and not the PE Environment.

I'm sorry, but you need to read more carefully, as winpe.wim looks a lot like a .WIM file to me. But thank you for the link. I was trying to be lazy, and just use WinToolKit to do the work for me, just using a few mouse clicks, and when it didn't work, I thought I'd ask about it. WIM to ISO is a function of the Toolkit, I simply did not know that this functionality was limited to only WIM images that contain a version of a Windows OS.

I'm just going to give Test 2 a quick spin, and see how it goes. I will report back in a little while. UPDATE 1 OK, 19 minutes later, I have 80 updates installed successfully. Even the peach one! I'm just installing it in a VM to verify everything. UPDATE 2 Yep, everything's fine in the VM, and all updates installed correctly. Many thanks Lego!

Peach, I could eat a peach for hours! Nice work Lego! Thanks.

OK, installing KB2771431 as a silent install worked perfectly. It shows up as an installed update, and everything is installed. I used 1.4.1.19Test1 for the integration.

Hardly the point of doing this, is it? EDIT, Going do do some testing, will post back later.

On the x86 version, the Toolkit fails to install KB2771431, with exactly the same error message. I think there is something in KB2771431 that the Toolkit does not like.

No, this was something I was playing with, and had moved in to that directory for ease of use purposes. If you install the official Windows 8 Deployment Kit, the official paths are... C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us And C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us

Ahh, thanks for looking in to this Lego. Is this something you will look at for the future one day? I guess not many people will play around with WinPE with the toolkit...

Title: 1 error(s) have occurred ErrType: Error (1.4.1.18) Description: Win Toolkit has recorded errors which occurred during integration and have been stored via '>> Details'. Exception: Exception: An error occured whilst integrating an update! Exception: Microsoft Windows [Version 6.2.9200] © 2012 Microsoft Corporation. All rights reserved. C:\Users\Tony\Desktop\WinToolkit 1.4.1-18>Set SEE_MASK_NOZONECHECKS=1 C:\Users\Tony\Desktop\WinToolkit 1.4.1-18>"C:\Windows\System32\Dism.exe" /Image:"C:\WinToolkit_Mount" /Add-Package /PackagePath:"D:\System Tools & OS's\Windows 8\Win8 x86 Hotfixes 27-2-13\Windows8-RT-KB2771431-x86.msu" /ScratchDir:"C:\Windows\Temp\WinToolkit\ScratchDir" /English Deployment Image Servicing and Management tool Version: 6.2.9200.16384 Image Version: 6.2.9200.16384 Processing 1 of 1 - D:\System Tools & OS's\Windows 8\Win8 x86 Hotfixes 27-2-13\Windows8-RT-KB2771431-x86.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f082e Error: 0x800f082e DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Users\Tony\Desktop\WinToolkit 1.4.1-18>exit ---------------------------------- EDIT, I just noticed another thread regarding this hotfix, it is for the 64bit version however, but please delete this thread if you feel it's redundant info. UPDATE Lego just addressed this issue in Build 19 Test 2

Hi Lego, the path is C:\WinPE\winpe.wim - as you can see, I'm playing with the Windows PE environment. I can make the iso, but if I look inside it, it's just winpe.wim inside an ISO file.

Hi Lego, Just wanted to report a bug in WIM Manager, that when you press the Make ISO button, there is nothing pre-populated in the folder to capture area, and is obviously unable to create an ISO file of the WIM. I'm using version 1.4.1.18 EDIT For the sake of clarity, I am trying to modify the Windows 8 WinPE.WIM, which is part of the Windows 8 Assessment & Deployment Kit.

Just FYI, but if any of you own a fairly recent Synology NAS (I own an 109+) DiskStation, and they have just released DSM4.2, which has the ability to setup the NAS so it can be a PXE/TFTP server. I haven't figured it out yet, but it seems to do a lot of the server work for you in one device.

Yeah, I have looked in to this a while ago. And found that you cannot partition this USB stick. It needs to be seen by the system as a fixed drive, but for whatever reason, Sandisk are not interested in helping their customers out with this, as it is a simple change to the drives firmware, like you described. There is a rumour going round that Sandisk are going to realease an updated firmware that will make this drive compatible with Windows To Go, and turn it into a fixed disk. I think that's unlikely, but you never know! Have a look here, it seems Sandisk support simply does not care.