The Gen 3 Intake Valve Problem Explained






Taking your vehicle in for an oil change is often nothing more than a mundane task. But sometimes, you can get a surprise you weren’t expecting. This was the case for many drivers when they took their Ford Mustang GT or F-150 with the Coyote 5.0 engine in to get their oil changed. Several drivers soon found out that their motor was burning more oil than it should’ve been due to an oil consumption issue that affected certain Ford Gen 3 engines from model years 2018 through 2020.

Despite being one of the best V8 engines ever made, the Coyote engine has had some issues, at least for certain vehicle model years. As Ford reported in a 2019 Technical Service Bulletin to dealerships, affected engines could consume over one quart of oil every 3,000 miles, with no visible leaks. The bulletin states that this issue could occur because the engine is creating a strong internal vacuum when fuel injection is temporarily reduced during deceleration. As a result, oil is pulled out of the crankcase and into the combustion chamber.

Ford instructed dealerships to inspect vehicles for any leaks, as this would indicate a different problem. If there were no leaks, dealerships were to drain the engine oil and replace the filter before refilling it and reprogramming a system called Powertrain Control Module. Depending on the model year, techs may have been directed to install an updated engine oil level indicator as well.

The Ford Coyote engine defect lead to legal action

Excessive oil consumption became a common problem with the Ford 5.0 Coyote engine, but many drivers didn’t even know something was wrong. Without the engine leaking oil, many affected Ford owners only found out about the problem when actively checking their oil or during routine maintenance. This in part is what inspired several owner complaints, and even legal action.

Multiple class action lawsuits have been filed alleging these vehicles consumed an excessive amount of oil. One such lawsuit specifically from owners of Ford F-150s from model years 2018 through 2020 was filed in Michigan federal court in August of 2025. The lawsuit alleges that in addition to the oil consumption issue, Ford failed to adequately inform consumers, instead only issuing technical service bulletins to dealerships. Plaintiffs in the lawsuit also allege that they were still expected to closely monitor oil levels and add more oil than is normally needed between service visits, causing them to suffer financial losses.





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


The Windows Insider Program is about to get much easier

Ed Bott / Elyse Betters Picaro / ZDNET

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Microsoft is making the Insider Program less complicated.
  • Beta channel will be a more reliable preview of the next retail release.
  • Other changes will allow testers to quickly enable/disable new features.

Last month, Microsoft took official notice of its customers’ many complaints about Windows 11. Pavan Davaluri, the executive vice president who runs the Windows and Devices group, promised sweeping changes to Windows 11. Today, the company announced the first of those changes in a post authored by Alec Oot, who’s been the principal group product manager for the Windows Insider Program since January 2024.

Those changes will streamline the Insider program, which has lost sight of its original goals in the past few years. (For a brief history of the program and what had gone wrong, see my post from last November: “The Windows Insider Program is a confusing mess.”)

Also: If Microsoft really wants to fix Windows 11, it should do these four things ASAP

If you’re currently participating in the Windows Insider Program, these are meaningful changes. Here’s what you can expect.

Simplifying the Insider channel lineup

Throughout the Windows 11 era, signing up for the Insider program has required choosing one of four channels using a dialog in Windows Settings. Here’s what those options look like today on one of my test PCs.

insider-program-channels-lineup-old

The current Insider channel lineup is confusing, to say the least.

Screenshot by Ed Bott/ZDNET

Which channel should you choose? As the company admitted in today’s post, “the channel structure became confusing. It was not clear what channel to pick based on what you wanted to get out of the program.”

The new lineup consists of two primary channels: Experimental and Beta. The Release Preview channel will still be available, primarily for the benefit of corporate customers who want early access to production builds a few days before their official release. That option will be available under the Advanced Options section.

windows-insider-channel-lineup-new

This simplified lineup is easier to follow. Beta is the upcoming retail release, Experimental is for the adventurous.

Screenshot courtesy of Microsoft

Here’s Microsoft’s official description of what’s in each channel now, with the company’s emphasis retained:

  • Experimental replaces what were previously the Dev and Canary channels. The name is deliberate: you’re getting early access to features under active development, with the understanding that what you see may change, get delayed, or not ship at all. We’ve heard your feedback that you want to access and contribute to features early in development and this is the channel to do that.
  • Beta is a refresh of the previous Beta Channel and previews what we plan to ship in the coming weeks. The big change: we’re ending gradual feature rollouts in Beta. When we announce a feature in a Beta update and you take that update, you will have that feature. You may occasionally see small differences within a feature as we test variations, but the feature itself will always be on your device.

These changes will apply to the Windows Insider Program for Business as well.

Offering a choice of platforms

For those testers who want to tinker with the bleeding edge of Windows development, a few additional options will be available in the Experimental channel. These advanced options will allow you to choose from a platform that’s aligned to a currently supported retail build. Currently, that’s Windows 11 version 25H2 or 26H1, with the latter being exclusively for new hardware arriving soon with Snapdragon X2 Arm chips.

Also: Microsoft account vs. local account: How to choose

There will also be a Future Platforms option, which represents a preview build that is not aligned to a retail version of Windows. According to today’s announcement, this option is “aimed at users who are looking to be at the forefront of platform development. Insiders looking for the earliest access to features should remain on a version aligned to a retail build.”

windows-insider-advanced-options-new

The Future Platforms option is the equivalent of the current Canary channel

Screenshot courtesy of Microsoft

Minimizing the chaos of Controlled Feature Rollout

Last month, I urged Microsoft to stop using its Controlled Feature Rollout technology, especially for builds in the Beta channel. Apparently, someone in Redmond was listening.

One of the most common questions we receive from Insiders is “why don’t I have access to a feature that’s been announced in a WIP blog?” This is usually due to a technology called Controlled Feature Rollout (CFR), a gradual process of rolling out new features to ensure quality before releasing to wider audiences. These gradual rollouts are an industry standard that help us measure impact before releasing more broadly. But they also make your experience unpredictable and often mean you don’t get the new features that motivated many of you to join the Insider program to begin with.

Moving forward, Insider builds in the Beta channel will no longer suffer from this gradual rollout of features. Meanwhile, the company says, “Insiders in the Experimental channel will have a new ability to enable or disable specific features via the new Feature Flags page on the Windows Insider Program settings page.”

windows-insider-feature-flags

Builds in the Experimental channel will include the option to turn new features on or off.

Screenshot courtesy of Microsoft

Not every feature will be available from this list, but the intent is to add those flags for “visible new features” that are announced as part of a new Insider build.

Making it easier to change channels

The final change announced today is one I didn’t see coming. Historically, leaving the Windows Insider Program or downgrading a channel (from Dev to Beta, for example) has required a full wipe and reinstall. That’s a major hurdle and a big impediment to anyone who doesn’t have the time or technical skills to do that sort of migration.

Also: Why Microsoft is forcing Windows 11 25H2 update on all eligible PCs

Beginning with the new channel lineup, it should be easier to change channels or leave the program without jumping through a bunch of hoops.

To make this a more streamlined and consistent experience, we’re making some behind the scenes changes to enable Insider builds to use an in-place upgrade (IPU) to hop between versions. This will allow in most cases Insiders to move between Experimental, Beta, and Release Preview on the same Windows core version, or leave the program without a clean install. An IPU takes a bit more time than your normal update but migrates your apps, settings, and data in-place.

If you’ve chosen one of the future platforms from the Experimental channel, those options don’t apply. To move back to a supported retail platform, you’ll need to do a clean install.

Also: Apple, Google, and Microsoft join Anthropic’s Project Glasswing to defend world’s most critical software

The upshot of all these changes should make things a lot clearer for anyone trying to figure out what’s coming in the next big feature update. Beta channel updates, for example, should offer a more accurate preview of what’s coming in the next big feature update, so over the next month or two we should get a better picture of what’s coming in the 26H2 release, due in October.

When can we start to see those changes rolling out to the general public? Stay tuned.





Source link