AutoPatcher no longer allowed


Recommended Posts

I had a call from Microsoft Legal this morning and they have told me that we are no longer allowed to endorse AutoPatcher on Neowin.

Microsoft will only allow updates to be downloaded from its own servers.

AutoPatcher started in 2003 and has been redistributed in some of the worlds best computer magazine cover CD/DVD's. I have no explanation for why Microsoft allowed it to continue unchecked for 4 years before making this decision.

I asked the representative if Windows Genuine Advantage had anything to do with it and he categorically told me this was not the case, he added that Windows Update for pre-Vista versions of Windows can now be accessed using Firefox and that the concern at Microsoft had more to do with the possible malicious code that could be redistributed with certified Microsoft updates.

We have no grounds to challenge the decision by Microsoft.

I'd like to thank the whole AutoPatcher team for their continued work, unfortunately none of the team is online, but they have been contacted via the AutoPatcher.com website by Microsoft Legal.

The AutoPatcher forums have been disabled for guests and members.

Link to comment
https://www.neowin.net/forum/topic/584427-autopatcher-no-longer-allowed/
Share on other sites

:(

It's great for packaging offline patches, portability, and in many ways more flexible than updating through Windows Update. What does Firefox access on WU have to do with that?? That's not nearly the reason I believe most are using AutoPatcher, and I think Microsoft is missing the problem here, or more likely, they either pretend or don't want to realize the problem. I mean, all Windows users have IE installed anyway, including Firefox users.

AP is more for system administrators and experienced users wanting to package files for easy offline installs, possibly on a network scale.

And of course they'll deny it's for WGA reasons. They don't want to get into the debate of locking in users to their services out of inefficient antipiracy methods again. They'd probably even lie to not have to.

While I don't see the need for MS to ban support for AutoPatcher, it is after all a great utility and something that has saved me hours and hours when repairing clients machines, I'm sure they (MS) must have their reasons for this.

I'll continue to support it as long as I can, but it is a massive blow to myself and to the community as a whole that MS have decided to take this action. But, as I've said there must be a good reason why, I'm sure it will all become clear in due course.

I'd like to express my thanks to all the team behind AutoPatcher for the sheer amount of hard work and dedication that they have all shown in making this product, and like others have said, it's a massive blow and it sucks - I feel for you guys.

Ad

Lets hope MS come up with there own solution for it I vaguely remember before XP SP2 they did a security rollup where several updates where in the one download.

I think it would be nice if they offered this every now and then a single download that has all the updates in it after SP2 perhaps they could have it make you register the PC after you have ran the updates on it making it possible to update peoples PC?s for them when they are on dial up etc.

Lets hope MS come up with there own solution for it I vaguely remember before XP SP2 they did a security rollup where several updates where in the one download.

I think it would be nice if they offered this every now and then a single download that has all the updates in it after SP2 perhaps they could have it make you register the PC after you have ran the updates on it making it possible to update peoples PC's for them when they are on dial up etc.

The single download isn't the point of AutoPatcher though. The cool thing about AutoPatcher is that you have a disc ready with the updates and you don't need to actually download the updates when setting up the computer, which can take quite a long time as it seems the XP update system seems to slow everything down. It also includes several optional updates that are never included in the infrequent rollups that Microsoft puts out. All in all, it's much more convenient to use AutoPatcher when compared to any solution Microsoft has ever provided.

This is a poor decision by Microsoft. I can understand their concern of being blamed if malicious code were distributed with their updates, but the AutoPatcher project has been going for 4 years without incident, so I'm at a loss as to why they would be concerned about this now.

Hi Guys,

It's a sad day and I don't mind saying that I am in shock here regarding the AP news.

I appreciate that the AP project is now dead as far as Neowin concerned, however I am wondering if there could be a future for it in another form?

Perhaps if the hotfixes and patches themselves are not re-distributed then MS would be able to live with it?

There are other projects which list the hotfixes for download or automate the download of the hotfixes directly from MS servers for offline use. If this could be combined with the AP framework then we could still have a viable project.

Folks would need to download the hotfixes themselves however once this is done the AP framework could still be useful for installing the hotfixes offline.

I have PM'ed some of the AP team with my suggestions so we will see what will come of it.

At the end of the day this is an attempt by MS to close down a freeware project that competes with their own automated patch distribution systems.

Anyone who thinks this has anything to do with security of the patches is deluding themselves.

Giving that MS had no issues with this project for over 4 years it seems strange for them to object now based on security concerns.

I am also disappointed that the Neowin Staff has let MS run roughshod over this project and done little to fight this action by MS.

Regards

Simon

What a crock of sh**. What is the crap about neowin is not allowed. Is Microsoft telling you what to do now neowin? Cant believe neowin will just do whatever it is told by Microsoft. Who is your daddy neowin lol. Wonder what will happen to http://www.ryanvm.net/msfn/ and sites like that if "Microsoft will only allow updates to be downloaded from its own servers."

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
    • Bypassed Windows 11 shows surprising stability on ancient, completely unsupported hardware by Sayan Sen When Windows 11 was first released, one of the most complained-about issues with the new desktop Microsoft OS was its higher system requirements, which pushed many relatively modern and powerful processors and devices onto the officially unsupported list. Thankfully, they have not been updated again for the base OS, though systems require four times the memory and storage if they want to run AI-powered apps and features. As such, Windows 11 technically runs on 4GB of memory, and there is no imposed restriction on the generation of memory it supports. Speaking of memory, prices are extremely high nowadays for hardware, especially DDR5 and DDR4 kits due to the current silicon shortage, and there are also reports of it affecting DDR2 as well, and it might only be a matter of time before even DDR1 gets affected. Before that could happen, an enthusiast took an ancient DDR1-based system and decided to try out Windows 11 on it to see how well the modern OS would fare on such hardware. The system runs an outdated graphics card interface standard based on AGP, or Advanced Graphics Port, called AGP 3.0 or AGP8x. AGP was essentially succeeded by the modern PCI Express (PCIe) bus standard. The user behind the experiment is retro hardware enthusiast Omores, who built the system around an ASRock ConRoe865PE motherboard based on Intel's i865PE chipset from way back in 2003, around the time when AGP was still in fashion. What made this board special back in the day was its unusual support for newer Core 2 Duo and even Core 2 Quad processors while still retaining older DDR1 memory support and an AGP8X graphics slot, making it an ideal bridge or link between two vastly different generations. Powering the machine was Intel's Core 2 Quad Q6600 alongside 3GB of DDR1 RAM and an ATI Radeon HD 4650 AGP graphics card, one of the final and most capable GPUs released for the aging AGP interface. While installing Windows 11 itself was relatively easy by bypassing Microsoft's hardware checks, getting the graphics card fully functional proved to be some challenge. Microsoft had quietly dropped native AGP support after the earliest releases of Windows 10, meaning newer versions of Windows no longer include the necessary Graphics Address Remapping Table (GART) drivers required for proper AGP acceleration. Without them, AGP graphics cards typically boot up, though with limited functionality, and can often throw a Code 43 error in Device Manager. To work around the limitation, Omores extracted Intel's legacy AGP440 SYS driver from an early Windows 10 release and paired it with a modified INF file so Windows 11 would correctly recognize the chipset. Following this and combined with AMD's final 64-bit Catalyst AGP drivers from 2012, the Radeon HD 4650 was able to operate with full AGP 8X acceleration intact. The result was said to be surprisingly usable for hardware that is over two decades old. Hardware-accelerated H.264 video playback worked correctly and benefited apps like Firefox, while legacy applications and games ran without major graphical issues. The system also successfully completed the 3DMark 2001 benchmark, although performance naturally lagged behind what the same hardware achieves under Windows 7, which is significantly lighter than Windows 11. There was, however, one unavoidable limitation as Microsoft's Windows 11 version 24H2 introduces a mandatory SSE4.2 CPU instruction requirement that cannot be bypassed through installer modifications or registry tweaks. Since no AGP-era processor supports SSE4.2, Windows 11 version 23H2 effectively becomes the final release capable of running on such systems. Regardless, it is still a very cool feat and quite fascinating to see just how stable Windows 11 turned out to be on such unfamiliar hardware. Source: Omores (Patreon) via O_MORES (Reddit)
    • That will only really help other players that are also responsible for creating the problem.
    • Well, it's good to know that they have found a workaround to a problem that they helped create, I guess...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!