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

    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
    • It is clear from this aricle that "Time Is On My Side" no matter which direction it is flowing., https://noai.duckduckgo.com/?i...m%2Fwatch%3Fv%3DsEj8lUx0gwY
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      577
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!