• Pim

    Pim

    @pim

    Viewing 15 replies - 121 through 135 (of 160 total)
    Author
    Replies
    • I can confirm that on my machine (i7-3740QM Win7 x64 Ultimate) KB4056894 was checked but as of today (Sat. Jan. 6) it is unchecked. The registry key is present. Of course I always follow MS-DEFCON, so I did not take my chances…

      1 user thanked author for this post.
    • in reply to: Patch Alert: Where we stand with this month’s mess #148280

      KB4011618 appears twice in my list with important updates, even after letting Windows search for updates again. WTH?

    • in reply to: RSS feed shows items with delay #142067

      [original content deleted. It seems that my browser and/or my RSS reader are playing up that require more research to make sure the problem does not originate at my end. My apologies for posting]

    • in reply to: MS-DEFCON 3: Get your August patches installed #132263

      What is the status of .NET Framework 4.7 on Windows 7 now that we have MS-DEFCON 3? Since a couple of weeks it is a checked important update, but we were at MS-DEFCON 2. Before that it was unchecked, so I did not install it yet.

    • Paul Thurrott has a very good article on this and especially why Windows as a (Dis)service is untenable and failing. It is a premium article, but if you just register without becoming a premium member you can read 3 premium articles per month for free.

      4 users thanked author for this post.
    • in reply to: MS-DEFCON 3: Get patched, but watch out for Outlook #123020

      This morning Outlook 2010 June 2017 update KB3203467 was (still) offered as an important update on my Windows 7 system, but unticked. It is not retired.

      2 users thanked author for this post.
    • in reply to: A most unusual Patch Tuesday #120720

      Those that still use a Vista machine do not have to install all updates mentioned on the Guidance for older platforms page, if the machine has been patched until the last Patch Tuesday in April. Some of the updates mentioned on that page have been published earlier when Vista was still supported and therefore are likely already installed. If you have patched a Vista machine until April, the updates to download and install manually from the table are: 4018271, 4018466, 4019204, 4021903 and 4024402.

    • @woody: the link to the patch for a localized Windows XP version at the bottom of Microsoft’s TechNet page you refer to, results in the update for Windows XP Embedded and not regular Windows XP (click on the link and then open Details: it says “Embedded” even though the title of the page says Windows XP SP3 and not Embedded). You may want to include a link to the Update Catalog in your article for those people who need the localized KB4012598. In Windows XP it is not possible to install a different language patch so falling back on the English version (which is correctly linked on the TechNet page) does not work.

    • Vista was already patched in March, when it was still in extended support. XP is indeed an extraordinary exception.

      1 user thanked author for this post.
    • It applies to any system, no (paid) custom support is necessary. MS has decided to make the update available for everyone, instead of only the corporations that pay for custom support. You can download the update manually via Microsoft’s Update Catalog. I do not know whether it would also show up in Windows Update when you scan for updates.

      I have not tested it, but I assume it will work because the update comes straight from MS.

      3 users thanked author for this post.
    • I remember a Windows 10 presentation by Satya Nadella (I believe it was the Windows 10 introduction presentation) in which he said: “We do not want you to like Windows, we want you to love Windows!”.  How far we are away from that now, even further than we were before. Carrots please, not sticks!

      3 users thanked author for this post.
    • I just read about 2 more old CPU’s on which Windows Update refuses to work after the April Windows 7 rollup, besides the Intel Celeron Dual-Core CPU T3000 that was already mentioned on the forum: an Intel Pentium Dual Core E5400 and an AMD Phenom II X4 955 Black Edition. Both processors date back to 2009. The links refer to the forum of a Dutch tech website.

      It makes you wonder how many more casualties are out there. Nice work Microsoft…

      2 users thanked author for this post.
    • I have heard conflicting information about Skylake — some say that all Skylake computers will receive Windows 7/8 updates, while others say that not all Skylake computers will receive Windows 7/8 updates.

      You can blame that on Micrsoft’s “art of communication”.  Nobody really knows the details and maybe even inside Microsoft they don’t know it yet. Officially only Skylake computers on Microsoft’s list are supported until EOL of the respective Windows version. That announcement was made in the beginning of 2016 and changed a couple of times, but always only with respect to computers on the supported computer list. That is where a lot of sites went wrong: they interpreted the change as a change for all Skylake computers, instead of only the ones on the supported list.

      If you read carefully, nothing has been said about those other Skylake computers, including custom build ones. Logically updates should have stopped back in 2016 if one takes everything that has been said literally. However, all Skylake systems still get updates until now. The big question is whether Microsoft will halt Windows Updates for those Skylake systems sometime in the (near) future. That is a question I haven’t seen any answer to yet.

    • Jim, just a small correction: Kaby Lake is the current generation, Skylake the previous, but still widely available. Kaby Lake has the update issue, Skylake not, but possibly in the future if it is not a computer from Microsoft’s “list”.

      1 user thanked author for this post.
    • in reply to: A solution to the blocked Kaby Lake/Ryzen updates? #109782

      On Github Zeffy already writes “I realize these scripts are not that user friendly. When I made them, I never anticipated this project blowing up like it has.

      So moving forward, I’m going to look into simplifying the process, possibly with some kind of Windows service that can patch wuaueng.dll in memory without actually modifying any system files, much like how UxStyle works. This would be much safer and also enable other possibilities that would otherwise be impractical with the xdelta/batch script setup I have now.

      If any of you have any ideas regarding this or want to help, feel free to comment!”

      Is this similar to your idea? > seems to be going in your direction if you read Titokhan’s comment there (or was that you 😉

    Viewing 15 replies - 121 through 135 (of 160 total)