pennsylvaniaron

rhahgleuhargh I just want to respond to your post before I delve into Thiersee's post. I know one of my tweaks is to stop IE11 from bringing up the IE welcome screen when you start it. From memory that welcome screen starts every time you open IE11. That's why that tweak is so important. The other tweak is to turn smartscreen to ON. Does your IE11 do that? regards...

pink, I just integrated a new iso with RDP. I took 2685811, 2685813 out of silent and put them as the last 2 updates after 4014565. Then my IE11 gets a black X and does not integrate. when I do the same exact creation with the 2685811, 2685813 in the silent section then no problems. No idea why yours works and mine doesn't. regards...

Thiersee thanks for your input. Since I changed the order of the silent updates I really don't have any issues that prevent me from making the iso. I'll try a new installation excluding the 2 updates pink_freud mentioned and I'll also include rdp this time. Lets see what that brings! ps...how come you only have that ONE update in silent? aren't 2603229 and 3046269 mandatory? thanks again... regards...

Hi Ron, I don't know, what it's going on with your installation, please append your actual .INI . here is my ini file. thanks 2017-04-20_22-21-PM_64_hp_convenience_4_11_17 final_edit.ini

Thanks for prompt reply. I just finished the April iso and here are my issues which may help others and why its the case with me I have no idea. My integration every month seems to fail when IE11 is being integrated. Last month I no longer integrated 2533552 and that seemed to repair the issue. this month a made a change to my silent update order which repaired that issue. I was using in my silent updates this order: 2603229, 3046269, 3177467, 2685811, 2685813. This made the IE11 update FAIL. All I did was put 3177467 ahead of 3046269, (in other words I switched their order) and left the other 3 updates where they were and now IE11 integrates perfectly and then the new monthly update. Someone in a prior post mentioned that 3177467 should go ahead of 3046269. A manual WU check on my VM comes up with Defender, MRT and 2813347. I told rhahgleuhargh about 2813347 last month. Its strange because rhahgleuhargh said its related to RDP which I don't integrate but its always an update for me and it DOES get successfully installed. Lastly regarding the telemetry vbs file. I know someone else wrote the script but if anyone who hasn't used it and tries to edit it and sees 5 updates a (4) and (11) its very confusing. Its bad enough when you have 5 updates the number in () is 4 and not a five, so if you add an update and have 6 updates the (4) now becomes (5). There should be some type of instructions just ahead of the hideupdates, "inside" the file. Also where does the -ai argument go if you want to use it?? Just my 2 cents. regards...

thanks thiersee. I'll keep 2603229, 3177467, 3046269, 2685811, 2685813 in the silent. I'll make the iso sometime tonight or tomorrow. regards...

ok cool. Can I assume the pre-reqs are still required? do 2603229, 3177467, 3046269, 2685811, 2685813 still go in silent? lastly (for now) I see there is no more rollup file to hide certain updates. do I need to do the new telemetry.exe and put in silent if my goal is to install win 7_64 (or x86) home premium with no intentions of upgrading to win 10? I am still weak on that hide updates file which if anyone cares I think needs to be updated. It still says (11) in the vbs file and its unclear if you add an update(s) which numbers need to be changed. here is the vbs statement>>>> Dim hideupdates(4) 'TO ADD 1 EDIT THE (11) AND ADD another hideupdates(#) so if you have 7 updates which numbers need to be changed and where does the -ai argument go? regards...

hi: I;m just back from vacation and just started on the April iso. I was using rick's dotnetfx462_full_x86_64_slim from 12/17/16 in the past and used the same link to check if it has been updated. The link is now different and the file heading date is 4_16_2016. Is that a typo and the date year should be 2017? or its correct and we should still be using the 12/17/16 file? regards...

Thiersee my beef is with MICROSOFT, unless I am misunderstanding. A "PREview" means BEFORE or something that is YET to come. So a PREVIEW KB such as kb4012218 released the 3rd Tuesday of MARCH should have in its description the following months name, in this case APRIL. But Microsoft names it a MARCH preview. (why because they release it in march??) I only bring this up because after I installed my MARCH iso with kb4012215 and then did a WU search for new updates, in the optional section of WU I saw this MARCH preview with kb4012218. At first glance since the kb's are only one number different (2215, vs 2218) I thought that for some reason my integrating of the real MARCH rollup (kb4012215) did NOT get integrated. Sorry if I am beating an old horse to death. I thought others who are reading and learning here might also get confused. Maybe its semantics. Once again thank you for all your help in the past. regards...

thiersee that's what I thought but the rollup kb4012218 says its the MARCH preview, not the APRIL preview. This is very confusing since we just integrated March's rollup kb4012215... regards...

hope everyone's weekend is going well. I noticed on my VM that after installing the latest 3/14/17 UL created iso, when checking updates on WU in the OPTIONAL updates there is kb4012218, which is the march preview monthly rollup. how does this differ from kb4012215 which we integrated for March? regards...

wow that's pretty drastic. The whole reason to make the iso is to install windows easily. without it win install is a big PAIN. while I have had my own issues, the one you're having is not one of them. You haven't given much info. are the updates in the correct order? 3125574 is the only update with a three (3-kb3125574) in front of it and naturally is in-between the 2's and 4's, so in the middle of the pack of updates. do not integrate 2532552. are you doing classic or convenience method? updates for _64 bit 2603229, 3046269, 3177467, 2685811, 2685813 go in silent section. if using home premium 3004375 not needed. hope that helps... regards...

rhahgleuhargh any idea why kb2813347 is asked as an important update on my win 7_64 HP vm by WU first time check? you said that update has to do with RDP which I do not integrate into my iso. if you're busy dont worry about it. Thx in advance for all your help. regards...

The only reason I excluded 2533552 was because of your tutorial which says to hide it or integrate via runonce and that YOU do NOT use it anymore. But for me at least when it is in the runonce (silent) list it screws up IE11 or the monthly rollup, not sure which. yes kb2813347 came as an IMPORTANT update and I do NOT integrate the RDP files in my iso. same file was asked in my January iso. regards...

rhahgleuhargh, Thank you for the reply. Why does 2533552 cause a problem? Isn't everyone integrating it? I just completed a VM with this method of excluding 2533552. WU asks for MRT, Defender, kb2813347. deep clean results, only 2534111. running sfc now: SFC passes. regards...

EUREKA! I have been working on this all day, trial after trial. The one change I made now lets IE11 to be integrated successfully. I did not integrate kb2533552 which I had previously been doing in my silent list. I removed it from the silent list (position #1). however, while watching all the updates get integrated one by one with a green check, after the last one, the monthly rollup update, wtk 1.5.4.10 progress list on the bottom says now integrating kb2533552, in addition to 2603229, 3046269 and 3177467. How is this possible if kb2533552 is not in the update list and not in silents? Although I do not understand why, she worked and I am now testing in VM environment. regards...

Is it possible our issues are "somewhat" related in that WTK is the issue? regards...

gentlemen, sorry to bother you again but it seems the last 2 times I have made an ISO with WTK, for some reason IE11 keeps failing to integrate. I eventually fix it but I cant remember what I did (if anything) but all of a sudden it works. Yes I know that sounds strange. I'm using wtk 15410, convenience updates (total 43, includes ie11). I believe I have all the updates where they belong and in the correct order as per the tutorial. I download the UL using WUD into a separate folder and then add them into WTK, pretty simple. I have 2 prereq's, 39 updates, then ie11, and lastly the 2nd round, 4012215. I used the 3_14_17 UL list just updated (THX). I have a screenshot and txt file of the error saved on my desktop but do not know how to post it. I get an error that I can only upload a certain amt of kb and if I try to paste it into this post using the boards editor it say my browsers security settings don't allow it. So that hinders me and is another issue. Bottom line is that I ASSUME one of the CONVENIENCE updates is causing IE11 to fail. once IE11 fails the new monthly rollup also does not integrate which is probably normal. I am using home premium orig. sp1 iso into new folder on desktop. Malwarebytes is disabled, nothing else running. I have tried using and eliminating 3004375 but it stills fails. All proper kb's are in the sfx section. FLASH>>>ok I am able to paste this part of the txt file. is it the new monthly rollup that's the problem (and has been)??? When integrating all the updates get a green check next to each one, then IE11 has that blue arrow next to it. It tries to integrate and eventually (1 min) gets a black X, then the new monthly rollup gets a blue question mark. regards... C:\Users\Ron Scalzo\Desktop\Slip Streaming> chcp 65001 C:\Users\Ron Scalzo\Desktop\Slip Streaming>Set SEE_MASK_NOZONECHECKS=1 C:\Users\Ron Scalzo\Desktop\Slip Streaming>"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\WinToolkit_Mount_A5D82EB639A7DDFA216ECF859B8D824B" /Add-Package /PackagePath:"D:\Win Toolkit\UL Updates_64\4-Windows6.1-KB4012215-x64.msu" /ScratchDir:"C:\Windows\WinToolkit_Temp\ScratchDir_D79615134E332C463D4505AFB114DCC8" /English Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.1.7601.23403 Processing 1 of 1 - D:\Win Toolkit\UL Updates_64\4-Windows6.1-KB4012215-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f082f Error: 0x800f082f 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\Ron Scalzo\Desktop\Slip Streaming>exit

ohh, I have never seen that splash screen before. I did see the mount "folder" location in options, misc, but took the splash screen language LITERALLY and was looking for an SSD option in its own right. My misinterpretation. Thanks for your reply. regards...

great news! I see that Liam has added a splash screen when WTK 1.5.4.10 starts warning about running an anti-virus and also about the advantages of using an SSD. The splash screens says to make sure the mount path is "set" to SSD. Anyone know how to do that? regards...

MRT (Malicious Removal Tool) has NEVER found anything malicious on my systems since its inception. Was I just lucky? Seems like a wasted resource of time and energy. Regards...

happy new year alpha_95. The key word is NEW. This blog helps me to be happy. Learning is always a happy activity. I wish you well. Regards...

can someone explain the rollup file for me. I have been using it in my convenience iso creation. I believe this has to do with hiding those 8 kb's in the (7z) file on page 1 of this blog. I'm not sure if they are related to having win 7 get upgraded to win 10 (or am I off base). if so win 10 isn't being offered in WUD any longer. Is it still necessary to hide those kb's or are they related to something else? sorry for newbie question... regards...

thank you. Happy new year. I will test and make new January iso. thanks again for keeping us updated... regards...

Silly error on my part. All is well in Pennsylvania USA. Lego asked me for a link to this blog so maybe he'll keep updating WTK to make our lives easier. I also sent him the link to all the issues with the convenience rollup kb3125574 so he'll be up-to-date on that. Thanks once again for the replies... regards...