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

    • You do you, I've just said that it first appeared in "home" version before it will be available in "work" one. I use Edge only because it still supports MV2 uBO extension even on Android - I'll switch when they stop.
    • I imagine that was a review or something? My reviews mostly contain a lot of images and galleries, but these are all webp too, but yeah it all adds up on the page load. Would help if you were more helpful with your critique instead of bitching and moaning like a Karen 😂 Because then we might be able to fix it for you.
    • If Valve refused to let them make the case, I wonder if they've already partnered with someone else to do it? The fact that they didn't seek permission/licence before diving straight in is incredible though
    • OpenClaw now has native mobile apps on iOS and Android by Karthik Mudaliar OpenClaw, the viral open-source personal AI agent, now has its own mobile app, available on both Android and iOS. Users can pair the app with an existing OpenClaw gateway and can start using new mobile-native features that are now available on the app. The app supports all the existing features you'd already have seen on OpenClaw's TUI, as well as some more, such as real-time and background Talk mode, action approvals, sharing from iOS, and optional access to device capabilities such as camera, screen, location, photos, contacts, calendar, and reminders. These features are available on both the Android and iOS versions of the app. What's important with these apps is that they don't run OpenClaw on your phone, but are actually just companion apps that require a running OpenClaw Gateway on an existing device, on macOS, Linux, or Windows via WSL2. To pair the app with your existing OpenClaw gateway, users need to run the command "/pair qr" on the TUI or existing chat interface, which brings up a QR code. Users can then scan this QR code to pair it up with the mobile app. There's also an option to manually pair the app by entering the host and a port. Previously, OpenClaw had been available on phones via WhatsApp, Telegram, Slack, Discord, Microsoft Teams, Matrix, and others. Now, with a native mobile app, the interface is much cleaner and more focused on just the OpenClaw, of course, with the added support for camera, screen, location, and more. It's important to note that OpenClaw comes with its own security warnings. There's always a chance of prompt injection with these tools, so users are recommended to double-check authentication, tool policy, sandboxing, and execution approvals rather than prompts alone. For users well-versed with the AI harness, a native mobile app makes it easier to approve an automation, share a link, use voice, or let an agent react to phone-side context.
  • Recent Achievements

    • First Post
      rosiecharles earned a badge
      First Post
    • Reacting Well
      Juan Dela earned a badge
      Reacting Well
    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      515
    2. 2
      +Edouard
      273
    3. 3
      PsYcHoKiLLa
      143
    4. 4
      Steven P.
      99
    5. 5
      macoman
      54
  • Tell a friend

    Love Neowin? Tell a friend!