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

    • I'm content with my dual charger for now, but this actually sounds quite nice - and it's less expensive than I was expecting. As for the company, they can name themselves "Nazirapist" for all I care.
    • While I miss Outlook for a couple of small things, I use Thunderbird now because I don't like how MS wants to force you to change things.
    • Chrome has history of being the browser everyone uses because Internet Explorer sucks, not realizing that Edge changed that, but people got into the habit of using Chrome. I use Brave and I've never been happier with a browser. It does what it is meant to do and gets out of the way.
    • Wino Mail -> Microsoft Outlook (the new one). Link: https://github.com/bkaankose/Wino-Mail Just sayin.
    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!