Jump to content

clarkg888

Members
 View Profile  See their activity

  • Posts

    60

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by clarkg888

  1. clarkg888
    Hello Lego, I have been getting this error at various points during integration of updates. Collection was modified; enumeration operation may not execute. I am starting integration with the virgin Windows 7 SP1 Ultimate. I am running Windows XP. The last version that I've used that works without this error is v1.5.0.12. I have seen this problem with versions 1.5.0.24, 1.5.1.5 and 1.5.2.9. The first run where this was encountered was on 23-Sep with version 1.5.0.24, the error occurred 3 times, but after clicking OK each time, the update was apparently integrated successfully (check mark) and the integration completed. However, the Windows installed with this integrated iso was showing one of the updates in Windows update, so it was not integrated properly. The second run where this was encountered was on 24-Sep with version 1.5.1.5. the error occurred 2 times. After clicking OK on the second error, this time the update integration failed (X). Then the integration hung on an update 3 updates later. I could not stop the AIO integration with the Cancel button. After the second run, I went back to version 1.5.0.12 and it worked without error with no other changes. The third run where this was encountered was on 3-Oct with version 1.5.2.9. The error occurred more often: 6 times up to update 341 of 519. The final error on update 369 was "Server did not respond (timeout) Refreshing list.". At this point, I cancelled the integration. I've attached the Settings.txt and the saved preset "x64 20140926.ini". Screen shots for the third run are at: https://dl.dropboxusercontent.com/u/15342505/20141003.zip Thanks, Clark. Edit: shoot, I wanted this to go to the bugs forum. You are welcome to move it to the properly place. Settings.txt x64 20140926.ini
  2. clarkg888
    Are the WinToolkit temp folders empty when you start? Perhaps there are leftovers from a failed dismount that need to be manually deleted. Clark.
  3. clarkg888
    Just to be clear, moving to silent installers is only required if the host machine is running Windows XP. You would not want to move it when running in the new os's. Clark.
  4. clarkg888
    Hi everybody, Just a heads up for anybody like me who is still running WinToolkit on Windows XP. If you try to integrate KB2966583, all subsequent integrations fail. It appears this update causes the Windows XP compatible version of DISM to stop working. I found confirmation of this here. I'll be putting this update into the Silent installers until I finally upgrade my computer to Windows 7. Clark
  5. clarkg888
    @Kelsenellenelvian: How do you know that this iso is warez? It is the exact same name as the legitimate iso one can download from Technet with the appropriate Technet subscription. Clark.
  6. clarkg888
    @Thiersee You may already know this, but the error you got is just a warning. It apparently can be suppressed. See this MSFN post. (Assuming you want to rebuild the 7Z SFX installer yourself or it's one you built). Clark.
  7. clarkg888
    For .NET 4.5.2, you can use abbodi1406's add-on here.
  8. clarkg888
    @mail4skwarka The author of WinToolkit has reverted the behaviour of the installer to the sequential install in the newer versions. Get the latest from here. You can update just the installer on your build by manually mounting and unmounting the install.wim. You don't have to do a complete run just to update the installer. Clark.
  9. clarkg888
    I'm a little late, but since I started this thread, I though I should post. I can confirm this issue has been resolved. Clark.
  10. clarkg888
    @cstrine13: I tried installing Win7x64 onto a 20GB disk in a virtual machine. During the first stages of the install it said there was not sufficient space. I'm not sure how 'smart' this calculation is and whether it would 'know' that that you've reduced the install size, even if you managed to do that. The install ended up being less than 20GB, so it needed some additional margin as well. If you're using Ultimate, you could use one of the other versions that doesn't install Language packs :g: Also, if you're on the edge, you could install to a larger, regular HDD then image the result to the CF. Hope this helps, Clark.
  11. clarkg888
    Thanks KEiGHT for your suggestions. I ran WinToolkit on the same install.wim with nothing added except I changed the VC_RedistInstaller to the beginning. I'm not getting any errors here. I then mounted the install.wim in WinToolkit and used the Wim Registry Editor. The screen shot is below. This is showing exactly the order I want. However, RunOnce is actually installing in a different order as I posted above. It is installing the updates in alphabetic order. This is Windows 7 SP1 x64 Ultimate. I'm building this in Windows XP and installing in a VMWare Player VM. I think Legolash2o's recent changes to the RunOnce installer are causing this. Clark.
  12. clarkg888
    @KEiGHT I *have* arranged the silent installs in the order I want using the arrow keys, but the RunOnce installer is re-arranging them. Let me make it more clear. In the saved session.ini, the order is: jre-windows-x64 jre-windows-i586 Silverlight_x64 install_flash_player_12_active_x install_flash_player_12_plugin sw_lic_full_installer VC_RedistInstaller Windows6.1-KB2533552-x64 Windows6.1-KB2603229-x64 Windows6.1-KB2592687-x64 Windows6.1-KB2862019-x64 Windows6.1-KB2908518-x64 Windows6.1-KB2830477-x64 Windows6.1-KB2923545-x64 Windows6.1-KB2685811-x64 Windows6.1-KB2685813-x64 Windows6.1-KB958559-x64-RefreshPkg Windows6.1-KB2652034-v2-x64 Windows6.1-KB2697737-x64 Windows6.1-KB2801466-x64 Windows-KB890830-x64 rootsupd rvkroots Windows6.1-KB2895729-v2-x64 zzMU The RunOnce log is saying it installed them in this order: Windows6.1-KB2533552-x64 jre-windows-x64 jre-windows-i586 Silverlight_x64 install_flash_player_12_active_x install_flash_player_12_plugin sw_lic_full_installer VC_RedistInstaller Windows6.1-KB2592687-x64 Windows6.1-KB2603229-x64 Windows6.1-KB2652034-v2-x64 Windows6.1-KB2685811-x64 Windows6.1-KB2685813-x64 Windows6.1-KB2697737-x64 Windows6.1-KB2801466-x64 Windows6.1-KB2830477-x64 Windows6.1-KB2862019-x64 Windows6.1-KB2895729-v2-x64 Windows6.1-KB2908518-x64 Windows6.1-KB2923545-x64 Windows6.1-KB958559-x64-RefreshPkg Windows-KB890830-x64 rootsupd rvkroots zzMU Notice that the "Windows6.1" updates have been rearranged into alphabetic order. On further examination, the problem I saw in previous builds with KB2895729-v2-x64 causing subsequent install failures is no longer occurring. Also, if I put VC_RedistInstaller at the beginning, I'll probably avoid the problem I'm seeing with it. However, there is another problem. The Virtual PC package Windows6.1-KB958559-x64-RefreshPkg is being installed *after* its updates Windows6.1-KB2652034-v2-x64, Windows6.1-KB2697737-x64, and Windows6.1-KB2801466-x64. So, those updates aren't getting installed. Clark.
  13. clarkg888
    Hi, The RunOnce installer is changing the order of installs I originally specified. The relevant part of the session .ini: #Silent Installs jre-windows-x64::/s WEB_JAVA_SECURITY_LEVEL=M;NO;29.27 MB;F:\Win Toolkit\Installs Win7 x64\jre-windows-x64.exe;Always Installed jre-windows-i586::/s WEB_JAVA_SECURITY_LEVEL=M;NO;27.79 MB;F:\Win Toolkit\Installs Common\jre-windows-i586.exe;Always Installed Silverlight_x64::/q;NO;12.47 MB;F:\Win Toolkit\Installs Win7 x64\Silverlight_x64.exe;Always Installed install_flash_player_12_active_x::-install -au 2;NO;16.50 MB;F:\Win Toolkit\Installs Common\install_flash_player_12_active_x.exe;Always Installed install_flash_player_12_plugin::-install -au 2;NO;17.06 MB;F:\Win Toolkit\Installs Common\install_flash_player_12_plugin.exe;Always Installed sw_lic_full_installer::/S;NO;11.56 MB;F:\Win Toolkit\Installs Common\sw_lic_full_installer.exe;Always Installed VC_RedistInstaller::/VERYSILENT /NORESTART;NO;47.68 MB;F:\Win Toolkit\Installs Common\VC_RedistInstaller.exe;Always Installed Windows6.1-KB2533552-x64::N/A (Not Needed);NO;9.23 MB;F:\WHD\Updates\Windows7-x64_no\Additional\Not Integratable\Windows6.1-KB2533552-x64.msu;Always Installed Windows6.1-KB2603229-x64::N/A (Not Needed);NO;193.42 KB;F:\WHD\Updates\Windows7-x64_no\Additional\Not Integratable\Windows6.1-KB2603229-x64.msu;Always Installed Windows6.1-KB2592687-x64::N/A (Not Needed);NO;6.80 MB;F:\WHD\Updates\Windows7-x64_no\Additional\RDP8.0\Windows6.1-KB2592687-x64.msu;Always Installed Windows6.1-KB2862019-x64::N/A (Not Needed);NO;3.80 MB;F:\WHD\Updates\Windows7-x64_no\Additional\RDP8.0 Updates\Windows6.1-KB2862019-x64.msu;Always Installed Windows6.1-KB2908518-x64::N/A (Not Needed);NO;1.47 MB;F:\WHD\Updates\Windows7-x64_no\Additional\RDP8.0 Updates\Windows6.1-KB2908518-x64.msu;Always Installed Windows6.1-KB2830477-x64::N/A (Not Needed);NO;6.43 MB;F:\WHD\Updates\Windows7-x64_no\Additional\RDC8.1\Windows6.1-KB2830477-x64.msu;Always Installed Windows6.1-KB2923545-x64::N/A (Not Needed);NO;5.23 MB;F:\WHD\Updates\Windows7-x64_no\Additional\RDC8.1 Updates\Windows6.1-KB2923545-x64.msu;Always Installed Windows6.1-KB2685811-x64::N/A (Not Needed);NO;791.24 KB;F:\WHD\Updates\Windows7-x64_no\General\Windows6.1-KB2685811-x64.msu;Always Installed Windows6.1-KB2685813-x64::N/A (Not Needed);NO;1.11 MB;F:\WHD\Updates\Windows7-x64_no\General\Windows6.1-KB2685813-x64.msu;Always Installed Windows6.1-KB958559-x64-RefreshPkg::N/A (Not Needed);NO;16.30 MB;F:\WHD\Updates\Windows7-x64_no\Extra\VirtualPC\Windows6.1-KB958559-x64-RefreshPkg.msu;Always Installed Windows6.1-KB2652034-v2-x64::N/A (Not Needed);NO;344.30 KB;F:\WHD\Updates\Windows7-x64_no\Extra\VirtualPC Updates\Windows6.1-KB2652034-v2-x64.msu;Always Installed Windows6.1-KB2697737-x64::N/A (Not Needed);NO;1.70 MB;F:\WHD\Updates\Windows7-x64_no\Extra\VirtualPC Updates\Windows6.1-KB2697737-x64.msu;Always Installed Windows6.1-KB2801466-x64::N/A (Not Needed);NO;715.33 KB;F:\WHD\Updates\Windows7-x64_no\Extra\VirtualPC Updates\Windows6.1-KB2801466-x64.msu;Always Installed Windows-KB890830-x64::/Q;NO;24.45 MB;F:\Win Toolkit\Installs Win7 x64\Windows-KB890830-x64.exe;Always Installed rootsupd::/q;NO;447.33 KB;F:\Win Toolkit\Installs Common\rootsupd.exe;Always Installed rvkroots::/q;NO;195.33 KB;F:\Win Toolkit\Installs Common\rvkroots.exe;Always Installed Windows6.1-KB2895729-v2-x64::N/A (Not Needed);NO;793.61 KB;F:\WHD\Updates\Windows7-x64_no\Hotfix\Windows6.1-KB2895729-v2-x64.msu;Always Installed zzMU::;NO;53.87 KB;F:\Win Toolkit\Installs Common\zzMU.exe;Always Installed I've attached the RunOnce log. It looks like it is sorting the items it considers 'updates' in alphabetic order. When I install, the VC++ 2005 and 2008 (x86 and x64) parts of VC_RedistInstaller (McRips installer) are failing with error 1935 (screenshot attached). I had seen this in the past and found that I needed to install VC_Redistributable before KB2592687. The RunOnce log is showing it being installed *just* before, but maybe they are being installed concurrently? Also, I wanted KB2895729 at the end as I had seen problems where subsequent updates would fail after installing KB2895729. Perhaps it needs a reboot? Ultimately, I think it would be best to install in the same order as shown in the AIO integrator. The integration was done with v1.4.37.7, then I mounted/unmounted in 1.4.37.17 to get the RunOnce updated. Thanks for this great tool, Clark. WinToolkit_RunOnce_Log.txt
  14. clarkg888
    A possible cause: When installing KB2895729 as silent, I have found it messes up subsequent installs, probably because it *really* requires a reboot. So I put it last in the list. Even if this resolves Thiersee's problem, having an option to reboot and continue more installations would be a good addition to WinToolkit. Right now, my builds focus on installing 'core' stuff I want on any PC (e.g. Flash, java, C++ redistributable, etc.) in the silent installers. Eventually, I'd like to add applications that are 'optional' to the list, but it would be much better to have a reboot before hand so that all the core stuff is stable. Clark.
  15. clarkg888
    BrokenZero0: I have successfully integrated WMF4.0 by using the .net 4.5.1 addon. You can also integrate Extra\NT.Backup.Utility As for the others: Additional\Not Integratable: obvious silent install Additional\SUR Tool: silent install Additional\WinRE: neither integrate nor silent: only makes sense to integrate to boot.wim Additional\Without Platform: I don't use Additional\WUClient EXE: integrate the .cabs instead Extra\BrowserChoice: I don't use, for Europe only Extra\DCA2.0 Updates: I don't use Extra\VirtualPC: silent install Extra\VirtualPC Updates: silent install
  16. clarkg888
    It's been quite a few versions back that I last used the autounattend.xml function in Wintoolkit, but... @Camex: WinToolkit creates the file, but you need to make sure you've put it in the root of the DVD image folder before you create your iso for install. It doesn't put it there automatically. If you already know this, my apologies. @WarZ: yes, there is no option in WinToolkit for that one. Since it is just one more click for me (accept US defaults), I haven't bothered to do the manual edits for this. Clark.
  17. clarkg888
    Well, if one is running WinToolkit Windows XP (like I do ) then you need to use the .cab
  18. clarkg888
    I don't believe WMF 4.0 can be integrated. You can put it in the silent installers instead. Clark.
  19. clarkg888
    I'm on about during integration so a right-click option wouldn't work. How about a right click to "move to silent" before integration has been started?
  20. clarkg888
    Regarding KB943790. The KB describes it as an update to be applied to winpe.wim, not the main wim. So, it doesn't look like it should be integrated OR silent installed. If anything, it should be integrated to the winpe.wim.
  21. clarkg888
    Outside of Wintoolkit, I get the same message. Just to confirm I didn't have a corrupt download, I ran it under Windows 7 fine.
  22. clarkg888
    Thanks for the explanation abbodi1406! I just checked a Windows 7 x86 installed from an image built without KB2726535: this KB says it adds South Sudan to the country list and I can see South Sudan in the list in the Region and Language control panel.
  23. clarkg888
    I am running WinToolkit on Windows XP Pro 32bit. I have been able to integrate the IE11 cab (Windows6.1-KB2841134-x86.cab) fine, but I decided to test integrating the .exe with the Test7 beta. I got this error: ...IE11-Windows6.1-x86-en-us.exe is not a valid Win32 application. I don't expect this can be fixed. This is just a notice to anyone else that is still using XP that you'll need to use the IE11 .cab to integrate. Clark.
  24. clarkg888
    Hello all, Using Wintoolkit test7, when I add IE11 as .exe or .cab, I get this message: Internet Explorer 11 requires the following updates to be integrated first: KB2726535 I am using RicaNeaga's hotfix repository posted here. It doesn't include KB2726535. McRip's repository did have this as a prerequisite for IE10, then later it was in the WU_Satisfy folder. I searched through that 'Windows 7 Hotfix repository' thread on mydigitallife and found where this KB superceded others, but no post indicating that this KB was superceded by another. The Microsoft article on IE11 prerequisites http://support.microsoft.com/kb/2847882 does not list this KB. Also, after I click OK on the message, IE11 is added. If I mouse over IE11, it displays a list of prerequisites but does not include this one. So it seems that KB2726535 is probably not a prerequisite. If that's the case, the check in Wintoolkit should be removed. Thanks, Clark.
  25. clarkg888
    I'm running the regular Windows XP Professional 32 bit.
×
×
  • Create New...