About AutoPatcher November 2006...  

178 members have voted

  1. 1. Pick what releases you want for November!

    • Full, Lite, Update, QMUP
      30
    • Full, Lite, Update
      40
    • Full, Lite, QMUP
      11
    • Full, Lite
      36
    • Full, QMUP
      36
    • Update, QMUP
      6
    • Update
      19


Recommended Posts

OMG nooooo :( i need update release, so what is WMP11 and IE7 is out you might aswell download it from microsoft plus there WGA protected and i speak for most people here that most people who use autopatcher are using it because there windows isnt legit so they won't have any use for these 2 files.

But i really need the Update Release as im formating my Computer soon.. i don't need no other release other then that one :(.

just my 2 coppers worth:

why dont we start having a regular schedule for full releases (Jan, Apr, July, Oct), with updates between. then if it is posted clearly and prominently, there will be fewer questions as to which is coming out.

Also, i vote update and QMUP

McG

I'm not sure if having a 'scheduled full' releases will justify issuing one out if it's less than a few dozen megs for an update.

Having said that, I'd prefer a full release...:)

I don't care much for the QMUP so my vote was null though.

Raptor - whatever you'll come up with - I, as I guess many here, will be most grateful for!

forget ie7 and wmp11 because uses wga check on install and unattended setup don't possible

autopatcher has to remain unattended during install because end users don't have much technician skills

i forgot to tell you that installer 3.1 v2 setup needs fixing because displays an anoying error during install

forget ie7 and wmp11 because uses wga check on install and unattended setup don't possible

autopatcher has to remain unattended during install because end users don't have much technician skills

i forgot to tell you that installer 3.1 v2 setup needs fixing because displays an anoying error during install

If you are afraid of wga check, don't install them :devil:

I agree with Project Mayu. The contents to be included. MS did not include WP11 nor .net v3 in November updates. Some of these updates were delayed for additional 2 days :angry:. I was brassed off because i thought ms normaly inc all updates 2nd tuesday of every month.

Greetings....

My understanding is that the Lords of MS have determined IE 7 to be in the category of critical security updates, however, to minimize the support load, they have decided to spoon feed distribution to the masses via Microsoft Update on a limited scale.

My opinion (free and you get what you pay for) is that this technically makes IE7 a go for inclusion with autopatcher XP if the intent is to help people maintain patched and secure systems.

On the flip side.... I've already run into a situation with a university using collaborative / white board software plug ins that have crashed gloriously after IE7 is installed. So yes.... there are some compatibility issues with 3rd party stuff.....

It boils down to whether the need is to keep autopatcher as a tool to keep current with the latest thinking at microsoft or to allow people who use autopatcher a chance to test for compatibilty issues.... how long will that take vs how soon do folks want a more secure / feature packed browser.....

Life is full of trade offs.... just ask my ex.....

You make a good point about IE7 being a security update, but IE6 SP2 is still in Microsoft's support lifecycle - and security patches will continue. IE7 still has compatibility issues (as you mentioned) so it should be optional until such time that IE7 is mainstream(Say, the retail release of Vista). It's like how AutoPatcher continued to support Windows XP SP1 after the release of SP2.

I think that there should be a Full release... Get the work done so you don't fall behind in any updates. And a QMUP to keep supporting those that use or depend on it.

Well, it seems to me that Autopatcher is intended to be used by the majority and not the minority. As long as IE6 is being used over IE7 by a significant percentage, it seems only logical to focus on IE6 still. I myself like IE7 and all, but it's use is not dictated by either myself or the use of AP.

CFT1119_102011128AB.png

According to Net Applications, you can see the current trends of browser usage as of Oct '06.I'd think if you set a threshold of IE6 to IE7 users, say a ratio of 60/40 respectively, then that would be a more appropriete time to change focus of which IE browser that AP is focused on.

Another alternative to consider is simply setting a timeframe down. Just make an announcement like "Autopatcher will no longer offer further support of IE6 after XX of 2007".

IE7 and WMP11 not important because nobody uses it

I don't like your tone of voice.

JC Denton (Deus Ex)

Full

With

IE 7

WMP 11

Dot net 3

and remove all old patches that don't apply to above, such as ie6 updates and dot net 2 as its in 3

All that + WD.

You make a good point about IE7 being a security update, but IE6 SP2 is still in Microsoft's support lifecycle - and security patches will continue. IE7 still has compatibility issues (as you mentioned) so it should be optional until such time that IE7 is mainstream(Say, the retail release of Vista). It's like how AutoPatcher continued to support Windows XP SP1 after the release of SP2.

WMP10 is optional, and so will be WIE7 and WMP11 (logically).

Well, it seems to me that Autopatcher is intended to be used by the majority and not the minority. As long as IE6 is being used over IE7 by a significant percentage, it seems only logical to focus on IE6 still. I myself like IE7 and all, but it's use is not dictated by either myself or the use of AP.

You've got point, but you're forgetting that there were months until the majority started using (for example) SP2 after it had been released.

You make a good point about IE7 being a security update, but IE6 SP2 is still in Microsoft's support lifecycle - and security patches will continue. IE7 still has compatibility issues (as you mentioned) so it should be optional until such time that IE7 is mainstream(Say, the retail release of Vista). It's like how AutoPatcher continued to support Windows XP SP1 after the release of SP2.

There may be a time in the not too distant future when MS support guru's respond to IE performance and security issues with the "just upgrade to IE 7" catch phrase to resolve reported issues and close vulnerabilities.....

Also... in the not too distant future.... if users have automatic updates enabled, as they should, then they will be receiving the IE7 install via WU... they will wake up one morning, launch IE7 and wonder "how did I get here?".... (saw david byrne just the other day... he's same as he ever was)... unless they have installed the IE7 blocking tool, that's going to be a very common scenario.... from my understanding everyone should be updated by Vista rollout to the masses late January... once IE7 is installed, embedded in the registry, etc.... one will have to essentially rebuild / reinstall XP SP2 to restore IE6 (this from experience).... also keep in mind that the Lords of MS have determined it far more cost effective to support only one version of IE....

If I'm understanding the intent of those hard working and dedicated folks that put together this wonderful gizmo called AutoPatcher (note... proper use of case....and respect).... it's to help us be able to patch/update either computer OS builds "built from scratch" or large and incomprehensible numbers of workstations... the process would drive even normal tech geeks (oxymoron) completely insane without the use of this tool.... how far ahead of the curb are our benefactors intending to stay?

Ok..... enough babbling on.... here's another log for the thought fire.... how long before MS realizes "hey... you know what... we need to patch IE7 because of the (fill in the blank) vulnerability...." .... this makes me wonder (humbly).... do the folks at autopatcher want to continue providing patches for both IE6 and IE7?.... what about size of D/L and bandwidth (considering that many of those using AutoPatcher do so because of lack of these)...

BTW to everyone working on AutoPatcher.... It's your project and do it anyway you see fit... Thanks very much and have a good holiday week... Happy Thanksgiving to everyone...

I remember that SP2 came out when AutoPatcher Full was near 250-300mb. With Microsoft not releasing SP3 for Windows XP for a year to come, I'm afraid that AutoPatcher releases will keep getting bigger and bigger. :(

Thats ok I have auotpatcher on a external 2.5 laptop hard drive enclosure, as long as it stays under 30 gigs i'll be happy :laugh:

well, if someone is thinking about remove old updates if ie7 or wmp11 is installed, forget about it. i've installed that just to see what can i found on windows update. i've found this list:

critical

KB873339

KB885835

KB885836

KB886185

KB887472

KB888302

KB890830

KB890859

KB891781

KB892130

KB893756

KB894391

KB896358

KB896423

KB896424

KB896428

KB898461

KB899587

KB899591

KB900725

KB901017

KB901214

KB902400

KB904706

KB905414

KB905749

KB908519

KB908531

KB910437

KB911280

KB911562

KB911564

KB911565

KB911567

KB911927

KB912919

KB913580

KB914388

KB914389

KB916595

KB917422

KB917953

KB918439

KB919007

KB920213

KB920214

KB920670

KB920683

KB920685

KB921398

KB922582

KB922616

KB922819

KB923191

KB923414

KB923789

KB923980

KB924191

KB924270

non critical

KB829019

KB900930

KB904942

KB909520

KB914440

KB920342

if someone wanna see by himself, there's updates for wmp 7, 9, 10 on that list. some of them are not listed even also updates for wmp10. and, by the way: autopatcher size is almost the same. i was unable to do an silent instalation for ie7 or wmp11, but i believe that it may be possible. if you bypass wga, it may work, but i believe that it will break the rules

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

    • No registered users viewing this page.
  • Posts

    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
    • Microsoft Edge 149.0.4022.52 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.52 changelog: Migration to improved V2 architecture for Workspaces. Workspaces, introduced in Edge in 2022, allows users to create durable sets of tabs that can be saved and shared with others. In order to improve reliability and performance of this feature, the following changes are being made: Migrating data for saved Workspaces from OneDrive/SharePoint to Edge Sync service Removing the collaboration/share functionality of this feature For organizations who have disabled Sync through policy, the existing v1 Workspace data will still be migrated to the new architecture. New v2 Workspaces created after migration won't sync across devices and will remain local to each device. This update occurs on a progressive rollout beginning in Edge Stable v145 and will continue rolling out in Edge v149. For more information, see Getting started with Microsoft Edge Workspaces. Feature Updates Passkey Sync for Enterprise Users. Microsoft Edge is introducing support for passkey synchronization for enterprise users, enabling secure, passwordless authentication across devices. Passkeys created in Edge can now be synced seamlessly, improving sign-in experience while maintaining strong security standards. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout. Enterprise WebView2 runtime downgrade via DowngradeVersion policy. Administrators can temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2) using the new DowngradeVersion policy in msedgewebview2.admx. The Downgrade Version policy allows enterprises to mitigate critical regressions by specifying per-application exe-to-version mappings. The Edge Updater installs the target version side-by-side, and the WebView2 Loader redirects targeted apps accordingly. Downgrades auto-expire with each new WebView2 release: apps pinned to N-1 remain on the same version (now becoming N-2) and will auto-update in the next release, while apps pinned to N-2 will revert to the current Evergreen version. The policy applies only to enterprise-managed devices (domain-joined or MDM-enrolled). For more information, see Microsoft Edge WebView2 Policy Documentation | Microsoft Learn. Collections retirement. Collections has been removed in this update. Users can no longer access or use the feature. To keep saved content, users can export it, or move all pages to Favorites before updating to Microsoft Edge Stable 149. For more information, see Organize your ideas with Collections in Microsoft Edge - Microsoft Support. Modern, unified, and updated Look and Feel. Microsoft Edge has updated the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This changes multiple elements of the UX such as spacing, corners, fonts, default colors, etc. Clarify choices surrounding third-party cookie settings. Language under Settings > Privacy, search, and services > Cookies are clarified to better describe the choices users have in managing third-party cookies. Custom primary password retirement. Users are no longer able to create a new custom primary password in Edge Settings edge://settings/autofill/passwords/settings. Any users who are still using a custom primary password will be automatically migrated to device authentication. Additionally, the PrimaryPasswordSetting policy will no longer support the WithCustomPrimaryPassword option. For more information, see Keep your saved passwords private in Microsoft Edge | Microsoft Support. Unifying Copilot Chat policy controls. The Microsoft365CopilotChatIconEnabled policy is the standard for configuring Copilot Chat. Previously, this behavior was controlled by blocking the Copilot extension, either explicitly or by using the * wildcard via the ExtensionSettings or ExtensionInstallBlockList policies. Extension and sidebar policies no longer affect the appearance or functionality of Copilot Chat. Copilot address bar suggestions were also tied to extension policy settings. Starting in Microsoft Edge version 149, admins can use the CopilotAddressBarSuggestionsEnabled policy to manage this behavior. Intune MAM Protected Downloads. The protected downloads feature for Intune MAM is now available for BYOD (Bring Your Own Device) devices, which aren't managed by a tenant. Policy Updates / New policies CopilotAddressBarSuggestionsEnabled - Enable Copilot address bar suggestions CpuPerformanceTierOverride - Override for the CPU performance tier DataUrlInWebWorkerOpaqueOriginEnabled - Enable opaque origins for data URLs in Web Workers DefaultLocalFontsSetting - Default Local Fonts permission setting ForceForegroundPriorityForUrls - Force foreground priority for specific URLs LocalFontsAllowedForUrls - Allow Local Fonts permission on these sites LocalFontsBlockedForUrls - Block Local Fonts permission on these sites Deprecated policies WalletDonationEnabled - Wallet Donation Enabled (deprecated) EdgeWalletEtreeEnabled - Edge Wallet E-Tree Enabled (deprecated) Additional policy changes ForceForegroundPriorityForUrls - ForceForegroundPriorityForOrigins is renamed to ForceForegroundPriorityForUrls OnSecurityEventEnterpriseConnector - Add macOS platform support ProtectedContentIdentifiersAllowed - Remove macOS platform support Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • User: "But is it good?" Microsoft: "Well, no. But it is less bad."
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      80
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!