Jump to content

[14 janvier 2020] Update list GDR pour Windows 7 SP1 x86/x64 (Fr-En-De-Es-It)


Recommended Posts

I am trying to get a grasp on this meltdown and spectre issue as it pertains to our UL's. The lastest UL's say NOT FOR AMD CPU's. Then there is the registry patch which is needed to get the lastest (january 2018) WU.

If I am doing a brand new win 7 install do I use the 12/12/17 UL's then run the patch and I am done or can I use the 1/9/18 with a computer with an amd cpu and run the patch?

can I integrate the NFW 4.7.1 by ricktendo (1/13/2018)

If using malwarebytes v.2 (not v.3) does this anti-virus have any influence on this procedure?

sorry for the confusion.

regards...

Link to post
Share on other sites
  • Replies 2.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Hello, Voici des Update Lists (UL) x86 et x64 à utiliser avec la dernière version de Windows Update Downloader (WUD), en partant d’un ISO de Windows 7 SP1. Elles reprennent le principe des m

Hello, J'ai trouvé une solution pour éviter l'installation mensuelle de MRT (et donc de l'emploi d'un leurre). C'est à confirmer, mais il semble qu'il suffit de créer cette clé:  

@phaolo, Please have a look in the Installers repack section of this forum. All of these programs can be integrated in "Silent installs + SFX" section of Wintoolkit with silent switches. @TheOtherJeff

Posted Images

5 hours ago, rhahgleuhargh said:

Hello,

Je viens de faire migrer un portable sous 7 vers 10 hier : la technique du GenuineTicket fonctionne toujours. Tu as donc encore le temps de réfléchir (ou au moins d'activer la licence puis de revenir à 7) !

Merci de l'info. Je ne suis pas certain que ça dure encore très longtemps ceci-dit...

Pour le moment j'ai installé le patch de Janvier mais je l'ai désactivé avec Inspectre de GRC, qui permet de vérifier si on est patché et surtout de désactiver les fix Meltdown et Spectre (il faut redémarrer):

Voici ce que ça donne chez moi avec un 6700K @4,4Ghz, une CM Z170, CrystalDiskMark x64 6.0 et un SSD 1To sous Windows 7 x64,

Meltdown off:
[b557dc48203b2d51ec1f5063c7321b73d15ddd0a

Meltdown on:
6a524337970b8da96cdf06fe83840959c6b53deb


47% de perfs en moins en écriture 4Ko-Q1T1, et le core 1 à 100% en lecture 4Ko-Q8T8 (il ne dépasse pas les 85% en off).

Les fix pour Spectre ne sont pas activés puisqu’il faut une màj du microcode.

 

 

 

___________________________________________________

 

Plusieurs chercheurs ont clairement indiqué que les patchs des navigateurs étaient relativement simples à contourner, la méthode la plus sûre est de désactiver/limiter le JavaScript (au moins pour les domaines de tierce-partie puisque normalement on a confiance dans le site qu'on visite).

Je recommande très fortement à tous d'utiliser uBlock Origin en mode medium, ça permet de bloquer les scripts (de tierce et/ou de première partie).
Sans-même utiliser de filtres, ce simple réglage aura pour conséquence de désactiver 99% des pubs et du tracking, mais là ce n'est plus seulement une question de confort et de vie privée, mais de sécurité.
Il faudra parfois ré-activer un script ou deux pour récupérer certaines fonctionnalités (typiquement les commentaires sur les sites qui les gèrent avec Disqus), mais le confort, le gain en vie privée et en sécurité est considérable et vaut le coup de s'embêter un (tout petit) peu plus.

 

Link to post
Share on other sites
22 hours ago, pennsylvaniaron said:

I am trying to get a grasp on this meltdown and spectre issue as it pertains to our UL's. The lastest UL's say NOT FOR AMD CPU's. Then there is the registry patch which is needed to get the lastest (january 2018) WU.

If I am doing a brand new win 7 install do I use the 12/12/17 UL's then run the patch and I am done or can I use the 1/9/18 with a computer with an amd cpu and run the patch?

can I integrate the NFW 4.7.1 by ricktendo (1/13/2018)

If using malwarebytes v.2 (not v.3) does this anti-virus have any influence on this procedure?

sorry for the confusion.

regards...

Anyone?

regards..

Link to post
Share on other sites

mooms thx for the reply.

Do you have an answer for the other question I posed?

If I am doing a brand new win 7 install do I use the 12/12/17 UL's then run the patch and I am done. Or CAN I use the 1/9/18 UL's with a computer if it has an amd cpu and run the patch. Lastly should we just wait for M$ to fix this before creating a new iso?

regards...

Link to post
Share on other sites

@pennsylvaniaron

Hi Ron,

which patch do you mean now?

Quote

Lastly should we just wait for M$ to fix this before creating a new iso?

This is a good idea :D!

BTW, I tested the add-on from abbodi1406 for NET-FW 4.7.1 https://www.wincert.net/forum/index.php?/topic/11127-microsoft-net-framework-471-for-windows-7/

it works very well!

Edited by Thiersee
Link to post
Share on other sites
53 minutes ago, pennsylvaniaron said:

mooms thx for the reply.

Do you have an answer for the other question I posed?

If I am doing a brand new win 7 install do I use the 12/12/17 UL's then run the patch and I am done. Or CAN I use the 1/9/18 UL's with a computer if it has an amd cpu and run the patch. Lastly should we just wait for M$ to fix this before creating a new iso?

regards...

Fix for AMD CPUs is available. But since January patch was buggy I suggest you to wait for the February Patch Tuesday, next Cumulative update will include all fixes. If you are in a hurry, use December UL to install your AMD machine, and then run the fix. Using January UL with an AMD processor (especially old one) will make your machine unbootable!

Link to post
Share on other sites
2 hours ago, Thiersee said:

@pennsylvaniaron

Hi Ron,

which patch do you mean now?

This is a good idea :D!

BTW, I tested the add-on from abbodi1406 for NET-FW 4.7.1 https://www.wincert.net/forum/index.php?/topic/11127-microsoft-net-framework-471-for-windows-7/

it works very well!

 

1 hour ago, rhahgleuhargh said:

Fix for AMD CPUs is available. But since January patch was buggy I suggest you to wait for the February Patch Tuesday, next Cumulative update will include all fixes. If you are in a hurry, use December UL to install your AMD machine, and then run the fix. Using January UL with an AMD processor (especially old one) will make your machine unbootable!

gentlemen just a word of thanks for all your input. I think sometimes asking these nubie questions may actually help others who might just be browsing the blog. While sometimes a little embarrassing (not knowing as much as a few others on this blog) I certainly have learned much. with that said:

thiersee, the patch I am referring to is the one that rhahgleuhargh linked in a post on pg.90. that's the registry fix to continue to get the January updates through WU. rhahgleuhargh's explanation above clears up the question I asked about which UL to use for a new ISO (or to wait).

1.) What I don't understand: what is in the January UL's that will mess up windows if using an amd cpu (especially and older one). If I was to use the January UL to make a new iso on an amd cpu then immediately run the registry fix (rhahgleuhargh link pg.90) shouldn't that be okay? Meanwhile I read that Intel cpu's are more vulnerable!

2.) The jan ul's and new iso aside, my main machine I built uses an amd fx-8350 cpu. I have the registry fix DL on my desktop but have NOT run it and I have not received the jan. updates through WU. If I run the fix I ASSume I will get the jan. updates through WU. But what will happen in February? Doesn't that reg. fix statement stay in the registry?

regards...

 

Link to post
Share on other sites

@pennsylvaniaron

My older AMD-CPU is a Turion X2 64bit (2007! :D): with this CPU I must use dec-UL (without KB4056894), otherwise windows does not start anymore!

With the next older CPU (AM3 Phenom II, all 4 cores enabled) no problem.

With FM2/FM2+ no problems too.

About the reg-patch:

it is related to the antivirus you are using; if you use MicrosoftSecurityEssential this reg-key is present in the registry after installing MSE.

Link to post
Share on other sites

@pennsylvaniaron

1- the .reg key is just to allow you to obtain the january patch for a non-updated machine. Most antiviruses are now updated and include the key in their updates.

2- you can activate the .regkey, if WU dectects your AMD processor it will install all fixes automatically, or nothing until next Update Patch.

Link to post
Share on other sites

To sum up:

  • The reg key is only needed for those who don't have any antivirus.
  • The January patch will not install if an incompatible AMD CPU is detected.
  • According to Thiersee, integrating the January patch will make Windows unbootable for older AMD CPU, so the safe way is to not integrate it at all, use the December UL, or wait for February patch that should fix the issue.
Link to post
Share on other sites
12 minutes ago, mooms said:

To sum up:

  • The reg key is only needed for those who don't have any antivirus......

Curious: just MSE installs this reg-key....

I was monitoring the registry during install of at least 10 VMs and exactly after MSE-Installation was finished, this key appeared in the registry.

Link to post
Share on other sites

I use malwarebytes and did some testing. I had been using v.2.2.1.1043. I have that version updated to the lastest MBAM updates and it does NOT add the registry key. No jan. updates came through WU. I then updated malwarebytes to v.3.3.1.2183 re-booted and the January updates 4056894 and 4055532 ARE available. also available in OPTIONAL updates is the preview of monthly quality rollup kb4057400.

fyi...

regards...

Link to post
Share on other sites
8 hours ago, Jan Krohn said:

Guys,

May I politely ask you to continue any discussion that's not in French in the appropriate sub forum? I've already received a complaint.

Thanks so much!

Jan

Hi Jan,

sorry, but which sub-forum would you propose for the update-lists?

This matter exists since 2014 as @rhahgleuhargh continued the work of @mooms if I remember well and it was from the beginning in French and English.

Sometimes I got an admonishment, because I answered in Italian and English to an Italian User and appended the translation in English: I was told the admitted language is French, but English is permitted too, if the user does not speak French.

Link to post
Share on other sites

Given the history of this thread, it makes little sense to split off the English discussion indeed.

I've dealt with it otherwise, and removed the complainant from this topic. If he so wishes, he can re-subscribe under the condition, that he will then be notified about new posts in any language, just as before.

Link to post
Share on other sites

Maybe we could create an "international version" of the topic and keep english message there, but it's ultimately the choice of rhahgleuhargh, since it's the author of the topic, and it will be more work for him, sine it will have to update and maintain two topics.

Or maybe someone can volunteer to create one (and update it when rhahgleuhargh update this one) ?

Link to post
Share on other sites

Hi,

I'm surprised that someone complained. And I don't think he/she is one of regular people writing here and helping me to improve the job (all of them can write in english). To my opinion, people complaining without helping should stay quiet.

Most of important posts are translated in French and English, so everybody can find the infos. Half of people reporting bugs or interesting things are not french, so no matters (at least to me) to answer in english. If you prefer you can move the post in International section (but in this case, french people won't be happy !). Create an english and a french topic is a little bit complicated since we'll miss some things. Or you can move this topic in International section specifying that people can write in english or french.

Je suis surpris que quelqu'un se soit plaint. La moitié des gens qui aident à maintenir ce topic ne sont pas français, et leurs remarques/infos sont très utiles. Je ne pense pas que cette personne soit l'une des habituées de ce forum, car la plupart des francophones d'entre nous écrit aussi en anglais. Donc celui/celle qui râle ferait mieux de se taire. On peut très bien déplacer ce topic dans la section internationale, mais dans ce cas, on ne pourra plus écrire en français ! Créer un topic séparé va compliquer l'affaire, on risque de perdre des infos utiles. A moins d'autoriser explicitement l'écriture en français et en anglais dans ce topic international ?

Edited by rhahgleuhargh
Link to post
Share on other sites

What am I missing here? I use both IE11 and google chrome which translate when you fellows write in French to English. I can't understand a word of French. Why is this an issue? I actually didn't want to write this post and debate this in this blog which should be reserved for it's intended title. Hopefully if after a few posts (if any) it's put to bed.

In addition whatever happens thank you rhahgleuhargh for ALL your efforts and hard, diligent work. And that goes for MANY others. You know who you are!

regards...

Edited by pennsylvaniaron
Link to post
Share on other sites

The complaint came through the spam feedback loop via Microsoft/Outlook.com. I've just noticed that he (or she) also complained about a few French language posts, not only the English ones - not to the moderators, not to me, but straight to Microsoft, accusing us of sending spam instead of just unsubscribing from the topic that he himself once actively subscribed to. When I'm thinking about it once more now, that kind of behaviour deserves at least a double facepalm.

The only sensible thing to do was removing the person from this topic. The issue should be solved now.

Thanks for your great work! I don't think we need to change anything about the thread.

Link to post
Share on other sites
7 hours ago, Jan Krohn said:

The complaint came through the spam feedback loop via Microsoft/Outlook.com. I've just noticed that he (or she) also complained about a few French language posts, not only the English ones - not to the moderators, not to me, but straight to Microsoft, accusing us of sending spam instead of just unsubscribing from the topic that he himself once actively subscribed to. When I'm thinking about it once more now, that kind of behaviour deserves at least a double facepalm.

The only sensible thing to do was removing the person from this topic. The issue should be solved now.

Thanks for your great work! I don't think we need to change anything about the thread.

Cheers!

regards...

Link to post
Share on other sites

Bonjour,
résultats de quelques tests x64 Home Premium sur une partition formatée :

En l'absence de la clé de registre nécessaire depuis ce mois, le résultat donné par WU est incohérent.
Avec la clé de registre tout se déroule bien avec 3 remarques sur 'lUL de janvier :
la KB3004375 est à mettre avec les versions Pro
la KB4040980 a bien été remplacé par la KB4054988
la KB3150513 est manquante dans la catégorie W10

J'ai donc rajouté la clé de registre dans mon SFX PackRunOnce qui est maintenant international.

Autres remarques :
Pour le DNF 4.x, c'est désormais uniquement le 4.7 qui est proposé.
L'installation de MSE ajoute bien la clé de registre.
L'installation de MSE active MU automatiquement sans aucune installation préalable.

@+

 

Link to post
Share on other sites

@icare

Merci pour ton retour !

Effectivement, sur une installation fraîche sans MSE, la clé ne s'installe pas. J'ajouterai le fichier .reg sur le premier post pour ceux qui n'utiliseraient pas ton SFX RunOnce (je l'utilise depuis toujours).

KB3004375 est bien dédiée aux versions pro mais comme elle est aussi nécessaire avec l'installation via le CR, je l'ai copiée également dans la catégorie Common (sur une installation via la méthode classique 2 autres mises à jour sont nécessaires pour les versions Pro Ultimate et Enterprise).

J'ai déjà viré KB4040980 de la prochaine version de l'UL suite aux infos d'abbodi1406

Je rajouterai KB3150513 dans la catégorie W10. Je ne me rappelle pas qu'elle m'ait été demandée avec le script pour masquer les mises à jour de télémétrie, je vérifierai.

Link to post
Share on other sites
23 minutes ago, rhahgleuhargh said:

Je rajouterai KB3150513 dans la catégorie W10. Je ne me rappelle pas qu'elle m'ait été demandée avec le script pour masquer les mises à jour de télémétrie, je vérifierai.

KB2952664 is a prerequisite for the installation of KB3150513, have a look here, so if KB2952664 has been masked out...

@icare

58 minutes ago, icare said:

la KB4040980 a bien été remplacé par la KB4054988

If I remember well, I had requests (Older patches) from WU if KB4040980 has not been installed; anyway I'll do a new test without this KB.

BTW: what is MU? Is the same as WU?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




×
×
  • Create New...