Thiersee Posted July 14, 2016 Share Posted July 14, 2016 @rhahgleuhargh Did you take the three .cab files (old WUClient) intentionally from the UL? Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 14, 2016 Author Share Posted July 14, 2016 @Thiersee Yes, they are useless. Confirmed by abbodi1406. Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 14, 2016 Share Posted July 14, 2016 (edited) Here's my challenge. I now have an excellent working win 7 iso with all the classic updates from 6/22/16. in addition nfw 4.61 wa and my personal tweaks, silent etc. what is the process now that a new updated UL (7/12/16) has been released. I really just want to get those new wu installed. do we have to start all over? take a NO UPDATES win 7 sp1 and use wtk with that? or do we extract the latest iso we made (prior month) into a new folder and load in the last preset (minus the updates), but include all the other items in the preset? since NFW is integrated already in the iso do we again include it as an add-on? regards... ps..just ran that june iso for the first time and malwarebytes found about 300 items in the c:\windows\inf\inf folder pertaining to asp.net 4.0, net clr networking, and many other entries, all Trojan agents. Edited July 14, 2016 by pennsylvaniaron Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 14, 2016 Author Share Posted July 14, 2016 @pennsylvaniaron If you want the most cleaner ISO, just start with a new process in an untouched ISO. But if you are in a hurry, exceptionnally, this month there are only 4 new updates. So you can use your previous ISO, let WU charge the new updates after installation, and run a deap-clean to remove the 3 superseeded updates. Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 14, 2016 Share Posted July 14, 2016 8 minutes ago, rhahgleuhargh said: @pennsylvaniaron If you want the most cleaner ISO, just start with a new process in an untouched ISO. But if you are in a hurry, exceptionnally, this month there are only 4 new updates. So you can use your previous ISO, let WU charge the new updates after installation, and run a deap-clean to remove the 3 superseeded updates. sorry another nubie question. how (where) do you do a deep-clean. I have seen you guys mention it a few times. regards... Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 14, 2016 Author Share Posted July 14, 2016 @pennsylvaniaron We told you a few pages ago ! Right clic on your system disk icon --> properties --> disk clean. It's possible that you have to check the option "clean system files" if proposed. The log file is in C;/Windows/Logs/CBS/ deep-clean.log. Removed updates are in the end of the file. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted July 14, 2016 Share Posted July 14, 2016 1 hour ago, rhahgleuhargh said: @Thiersee Yes, they are useless. Confirmed by abbodi1406. Can you give me a link? Because in his post #10467 on MDL he said "superseded but still checked by WU". Quote Link to comment Share on other sites More sharing options...
Pink_Freud Posted July 14, 2016 Share Posted July 14, 2016 1 hour ago, Thiersee said: Can you give me a link? Because in his post #10467 on MDL he said "superseded but still checked by WU". Link here: Regards Pink Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 14, 2016 Author Share Posted July 14, 2016 On 22/6/2016 at 4:12 PM, abbodi1406 said: yes i know that WU checks the state of WUClient-SelfUpdate .cabs on each search session but it completely runs fine without them, and WU itself mention that they are not required WindowsUpdate.log -> SelfUpdate is NOT required. Here it is. Thanks Pink_Freud ! Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 14, 2016 Share Posted July 14, 2016 3 hours ago, rhahgleuhargh said: @pennsylvaniaron We told you a few pages ago ! I appreciate your patience! I help people much less knowledgeable than me on other computer issues. It can be frustrating. Thanks again to all for helping me and hopefully as I read each post I will understand more... regards... Quote Link to comment Share on other sites More sharing options...
Alpha_95 Posted July 14, 2016 Share Posted July 14, 2016 (edited) Salut, paramètres WUD:http://i.imgur.com/ZuMEAg8.jpg paramètres WTK:http://i.imgur.com/w4gCqrL.jpg Intégration WTK:http://i.imgur.com/XC334wn.jpg ensuite, je sélectionne le reste excepté les mises à jours: Windows6.1-KB2506143-x64.msu 5-Windows6.1-KB2533552-x64.msu 5-Windows6.1-KB2603229-x64.msu 5-Windows6.1-KB3046269-x64.msu WTK me demande de les déplacer dans RunOnce donc je le fait manuellement vu les problèmes rencontrés... A ce stade, aucune modification dans WTK, pas de SFX, aucune suppression de composants etc... Intégration des mises à jours. Montage du fichier .wim dans C:\WIM (avec WTK) puis je copie les mises à jours manquantes (cf ci-dessus) en y incluant : - Windows6.1-KB2506143-x64.msu - 5-Windows6.1-KB2533552-x64.msu - 5-Windows6.1-KB2603229-x64.msu - 5-Windows6.1-KB3046269-x64.msu - ic-DNF46, - DXrt32, - DXrt64, - ic-Leurre-MRT, - ic-Silverlight, - ic-RunOnce, - W10.exe Exécuté au premier démarrage, les addons d'icare sont à jours. Redémarrage de la VM puis vérification avec windows update. Résultat: KB3164025 (mise à jour de NF4.6 si j'ai bien vu) KB2603229 (donc y a juste celle ci qui pose problème ?) KB3173040 (peut être caché avec le script w10 non ?) Aucune erreur dans les logs WTK. Windows 7 Pro x64 2016-07-14_18-14-PM.ini edit: Pour le rollup,y a quoi comme changement exactement pour l'intégration ? Faut toujours inclure les mises à jours en RunOnce: 5-Windows6.1-KB3046269-x64.msu 5-Windows6.1-KB2533552-x64.msu 5-Windows6.1-KB2603229-x64.msu re edit: Rollup testé en suivant ta capture d'écran avec les addons d'icare (DNF, MRT et Silverlight). et c'est tout. Je n'ai pas exécute les mises à jour de la catégorie 5 je précise. Quote KB3164025 Mise à jour NF 4.6.1 (normal je pense) KB3046269 KB2603229 KB3173040 KB976932 En facultatif: Quote KB3102429 Redémarrage et en live les mises à jours de la catégorie 5, redémarrage puis windows update : Quote KB3164025 Mise à jour NF 4.6.1 (normal je pense) KB3046269 (56ko) KB3173040 Windows Defender 1.225.1250.0 Merci pour ton aide et tes explications. Edited July 15, 2016 by Alpha_95 Quote Link to comment Share on other sites More sharing options...
winproof Posted July 15, 2016 Share Posted July 15, 2016 hello cool, une liste des updates a jours dans le futur! (22 juillet ) possible d'en avoir une en date du 1 aout 2017? comme ça on sera tranquille pour un moment bravo pour ton boulot! Quote Link to comment Share on other sites More sharing options...
Thiersee Posted July 15, 2016 Share Posted July 15, 2016 I hope you see that the list-date is correct; only the thread-title is wrong ! Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 15, 2016 Author Share Posted July 15, 2016 @pyr8 Merci beaucoup ! Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 15, 2016 Author Share Posted July 15, 2016 6 hours ago, winproof said: hello cool, une liste des updates a jours dans le futur! (22 juillet ) possible d'en avoir une en date du 1 aout 2017? comme ça on sera tranquille pour un moment Hello, Désolé, mais je ne vois pas où la date est dans le futur ? Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 15, 2016 Author Share Posted July 15, 2016 (edited) @Alpha_95 Je n'ai jamais rencontré de souci avec KB2603229 et KB3046269 intégrées en RunOnce avec l'installateur de WTK ou en setupcomplete.cmd, que ce soit avec la méthode classique ou via le Convenience Rollup. Je n'utilise pas ta méthode. Pour le reste, c'est correct au niveau des réglages. La différence est que tu installes le Framework management, peut-être que la cause est là. A intégrer avant le Rollup dans tous les cas pour en avoir les composants à jour. As-tu essayé de l'installer dans les prérequis ? Pour W10, je n'ai pas encore publié la mise à jour, je voulais envoyer un lien avec le maker, mais j'ai rencontré des soucis de taille de fichier uploadé. Pas le temps pour l'instant. Edited July 15, 2016 by rhahgleuhargh Quote Link to comment Share on other sites More sharing options...
Alpha_95 Posted July 15, 2016 Share Posted July 15, 2016 je l'ai montré plusieurs fois, WTK en runonce me pose des problèmes donc je ne peux pas faire autrement... Dans le rollup, je n'installe pas la KB2506143 donc le problème est ailleurs... http://imgur.com/cfEzlOR http://imgur.com/hadqnQq Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 16, 2016 Share Posted July 16, 2016 (edited) after my successful 6_22 and 7_12_16 win 7_64 home premium iso creations I am getting 361 Trojan agents being detected. I am using a VM. I have taken the iso and extracted it into a new folder via WTK. In the preset I add my tweaks, silents, and nfw 4.61 add-on. I then go into the silents and remove everything except the 4 needed kb's. I do not remove ANY components. when wtk does it thing all the updates get a yellow check (very fast, I think there were 192 using classic method). other than the add-on and the updates I don't think its any personal "thing" I am doing. that whole compilation takes 3.5 minutes. I then make the iso and do a new VM install. First thing I do is go to the internet, download malwarebytes v.2.2.1.1043. I check the box to also search for rootkits and do a THREAT scan. MBAM finds 361 Trojan agents in the c:\windows\inf\inf directory. sub dir are windows workflow foundation, net memory cache 4.0, asp.net, asp.net_4.0.30319, SMSvchost 4.0.0.0 and a few others. MBAM will successfully remove them all. Are these false positives? Are others getting the same results? I have never seen this before. In the past I always have run a threat scan as part of my initial setup and it has never detected anything. It is the heuristic (last part) of the scan that finds all 361. regards... Edited July 16, 2016 by pennsylvaniaron Quote Link to comment Share on other sites More sharing options...
Pink_Freud Posted July 16, 2016 Share Posted July 16, 2016 56 minutes ago, pennsylvaniaron said: MBAM finds 361 Trojan agents in the c:\windows\inf\inf directory. sub dir are windows workflow foundation, net memory cache 4.0, asp.net, asp.net_4.0.30319, SMSvchost 4.0.0.0 and a few others. MBAM will successfully remove them all. Are these false positives? Are others getting the same results? I have never seen this before. In the past I always have run a threat scan as part of my initial setup and it has never detected anything. It is the heuristic (last part) of the scan that finds all 361. regards... Same result here on fresh install VM:resul.txt Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 16, 2016 Share Posted July 16, 2016 Do you believe this is a nfw 4.61 add-on issue?? Guess the only way to find out is to do another install without that add-on. I cant do it for a number of hours so if you have tried it plz let me know. will save me some work. regards... Quote Link to comment Share on other sites More sharing options...
Thiersee Posted July 16, 2016 Share Posted July 16, 2016 I don't know, what you've installed, here my MBAM-test VM with Win7 Prof x64, German, WUD Convenience Rollup, WTK, my 55 standard-programs, NFW 4.61 Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 16, 2016 Share Posted July 16, 2016 40 minutes ago, Thiersee said: I don't know, what you've installed, here my MBAM-test VM with Win7 Prof x64, German, WUD Convenience Rollup, WTK, my 55 standard-programs, NFW 4.61 yes thiersee its weird. at least this time I have company! As I said I never gotten this before with all the other iso's I have made. I have time later to try another classic from 7_22 ul with no tweaks, no nothing except the updates. will report.. regards... Quote Link to comment Share on other sites More sharing options...
Pink_Freud Posted July 16, 2016 Share Posted July 16, 2016 (edited) 1 hour ago, Thiersee said: I don't know, what you've installed, here my MBAM-test In my case I'm using Classic update (DISM) & WTK abbodi1406 dotNetFx461_x64.W7.20160714.WA addon: http://www.wincert.net/forum/index.php?/topic/11127-microsoft-net-framework-461-for-windows-7/ Edited July 16, 2016 by Pink_Freud Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted July 16, 2016 Author Share Posted July 16, 2016 Hello guys, I don't think it's due to updates, they are M$ ones ! False positive due to the Addon ? In my case I use icare's DNF file, not an Addon. Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted July 16, 2016 Share Posted July 16, 2016 29 minutes ago, rhahgleuhargh said: Hello guys, I don't think it's due to updates, they are M$ ones ! False positive due to the Addon ? In my case I use icare's DNF file, not an Addon. 2 hours ago, Pink_Freud said: In my case I'm using Classic update (DISM) & WTK abbodi1406 dotNetFx461_x64.W7.20160714.WA addon: http://www.wincert.net/forum/index.php?/topic/11127-microsoft-net-framework-461-for-windows-7/ ok about to test w/o the nfw add-on. I am using a slightly older add-on from 051816. I didn't know that new one was out. apparently both (or no NFW add-on) gives the Trojan agents. I'll report back soon... regards... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.