Jump to content

pennsylvaniaron

Basic Sponsor
  • Content count

    324
  • Joined

  • Last visited

  • Days Won

    1

pennsylvaniaron last won the day on July 14 2016

pennsylvaniaron had the most liked content!

About pennsylvaniaron

  • Rank
    Priest

Profile Information

  • Gender
    Male
  • Location
    PA, USA
  • OS
    Windows 7 x64
  • Country
    United States

Recent Profile Visitors

1,328 profile views
  1. wtk 1607 released. I couldn't remove the av.reg tweak from the tweaks section (I had reason to in testing.) liam has now fixed that bug. fyi... regards....
  2. thx mooms and thiersee for your replies. very helpful. thiersee I sent you a PM with more information. regards...
  3. 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...
  4. Liam has repaired WTK v.1.6.0.5. Will give it a test now... FYI regards...
  5. 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...
  6. 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....
  7. My cpu is an apu It's an amd A6-3420m with radeon HD graphics. Its not that old. No I did not install the registry key. I was waiting for the fix but it looks like it did not get fixed (at least not for me) regards...
  8. I am on holiday in Florida. I have my laptop with amd cpu with win 7_64 HP. The last quality update I received was KB4054518 (12/15/17). I also received kb2952664 (2/9/18). I just did a manual WU and no new updates. Shouldn't I be receiving kb4074598? regards...
  9. 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...
  10. 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...
  11. 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...
  12. 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...
×