Jump to content

pennsylvaniaron

Basic Sponsor
  • Posts

    400
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by pennsylvaniaron

  1. I just completed my iso using wtk 1605 on my VM. I have 6 updates when initially running WU. They are

    4041083 & 4049016 (have to do with nfw security), 3185319, 2676562, 3123479, 3118401

    i was told to put the av.reg file in tweaks and 4099950 in silent installers, position #1...

    I installed the above 6 updates successfully, then did a deep clean. files that were superseded are 2534111, 2685811, 2685813 (these 2 I install with all the updates).  I am using the convenience method.

    everything seems fine but aren't these 6 updates too many for the initial WU check?

    regards...

  2. Guys I was away on vacation for 12 weeks. Tried following the last page or 2 of posts, but difficult without actually doing tests on a VM. 

    I will be using the April UL's. I only make the x64 version of home premium. I'll also be incorporating ricktendos NFW 4.7.1 (1/13/2018) in my silent list. I'll be using WTK1.6.0.1. I see that there is a WTK v.1.6.0.5 on the public page, but I get an error every time I start it. Is this a known problem?

    Will I have to add the AV.REG file to WTK tweaks? Is that regfile still necessary to continue to get future WU?

    Anything else to be on the lookout for?

    regards...

  3. 11 hours ago, rhahgleuhargh said:

    @pennsylvaniaron

    The keyreg is a mandatory step to get further updates proposed by WU. Have a look here . Most of antivirus install it (Windows Defender, MSE for M $ ones). But if you do not use antivirus, it will not be installed.

    I use malwarebytes v.2.21.1043. There is a v.3 out awhile. I guess v.2 does not do the key. I will do it manually.

    thank you,

    regards....

  4. 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...

  5. 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...

  6. 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...

  7. 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...

     

  8. 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..

  9. 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...

  10.  

    2 hours ago, rhahgleuhargh said:

    Temporary changelog for this month:

    Security Monthly Quality Rollup: KB4056894 replaces KB4054518 (common), KB2647753, KB3101722 x64, KB3084135 x64, KB3022777 x64, KB3092627 x86, and KB2862152 x64 (classic)

    I haven't received the KB4056894 to my main computer. Last monthly rollup is KB4054518. Just tried to do a manual WU and no new updates available. Sorry but the last page of replies to the forum I really don't understand:huh:. Shouldn't I have gotten kb4056894 automatically yesterday?

    lastly will new ul's be posted for january. I see 12/12/17 are the latest or should I just download the kb4056894 MSU or skip this month? any effect on amd cpu?

    regards...

  11. 10 minutes ago, J.J. said:

     Not sure if this was intentional but I (actually NTLite) found a duplicate update in your list.

    The "2-Windows6.1-KB3004375-v3-x64" update is located in "Common Convenience Rollup and Classic integration Updates" AND "Classic integration Updates (Professional, Ultimate, and Enterprise Editions ONLY)" categories.

    Im running Professional Edition, so I integrate either way. If it is truly Pro and higher only then some may not need.

    I am running Home Premium and was told to disregard 3004375, so I do NOT integrate. I did once and a deep clean uninstalled, said it was superseded.

    thx for the heads up!

    regards...

  12. 9 hours ago, mooms said:

    You should report it to Liam.

     

    6 hours ago, Thiersee said:

    Liam forgot a debug option checked "Boot.wim Test"!

    Go into "Options" (at the bottom) and uncheck it, then it can start the integration.

    BTW, there is a thread to report bugs...

    thx I emailed Liam about it. Seems like an easy fix and oversight by Liam. I know there is a thread for bugs but bring attention to it here at this thread because it is the main tool we use to keep our win 7's slipstreamed and figured it would be of interest to other members.

    regards...

×
×
  • Create New...