Forced Chrome Update by Crashing Windows: Difference between revisions
Set an Irrelevant notice. |
m Remove placeholder templates to avoid categorizing as needing work |
||
Line 1: | Line 1: | ||
{{Irrelevant}} | {{Irrelevant}}Since August 2024 i noticed that Chrome forces its own update by crashing windows10 (bluescreen) while playling YouTube videos. | ||
==Background== | ==Background== | ||
I have been doing electronics since the Apple ][ and the C-64. My whole life, I had no one to ask for information or help, as computing at home—and for most people at work—was completely new. So I think I can say that I know what I’m talking about because computers weren’t just my hobby; later, computers and electronics became my profession as well. I learned the most difficult and complex things, so everything else was and still is easy. With this in mind, you can understand why I believe the growing mass of truly dumb people is a problem—and that these problems will soon escalate dramatically, because holding a cellphone right does not make you intelligent. And yes, I have been coding since the Apple ][. | |||
$2 | $2 | ||
==[Incident]== | ==[Incident]== | ||
I have noticed that Chrome forces its own update by causing a Windows crash (bluescreen). The crash seems to be deliberately triggered to bypass update restrictions and ensure that Chrome updates itself upon reboot. This has been happening since August 2024. | |||
I have several identical laptops, all running Windows 10, some with Chrome from November 2024. The ones where Windows Update and Chrome Update are disabled crash while watching YouTube videos. The laptops that receive updates do not crash. I even have made identical drives to test this. | I have several identical laptops, all running Windows 10, some with Chrome from November 2024. The ones where Windows Update and Chrome Update are disabled crash while watching YouTube videos. The laptops that receive updates do not crash. I even have made identical drives to test this. | ||
Line 13: | Line 13: | ||
At first, I thought this was because I had set Windows Update to pause for seven days. Then I tested completely disabling updates, and in all cases, Chrome crashes Windows to force its update. It’s as if Chrome says, *"You won’t update me? I’ll wait a few days… but then—"* You get the idea. | At first, I thought this was because I had set Windows Update to pause for seven days. Then I tested completely disabling updates, and in all cases, Chrome crashes Windows to force its update. It’s as if Chrome says, *"You won’t update me? I’ll wait a few days… but then—"* You get the idea. | ||
All Chrome versions since August 2024 behave this way, even though the updater is disabled—blocked by system permissions (`no execute, no read`) and even deleted. Windows Update is also disabled through the registry, preventing write and read access to specific files. | All Chrome versions since August 2024 behave this way, even though the updater is disabled—blocked by system permissions (`no execute, no read`) and even deleted. Windows Update is also disabled through the registry, preventing write and read access to specific files. | ||
===[Company]'s response=== | ===[Company]'s response=== | ||
I did not tell google, they surely know... | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Latest revision as of 01:22, 23 February 2025
⚠️ Article status notice: This Article's Relevance Is Under Review
This article has been flagged for questionable relevance. Its connection to the systemic consumer protection issues outlined in the Mission statement and Moderator Guidelines isn't clear.
If you believe this notice has been placed in error, or once you have made the required improvements, please visit the #appeals
channel on our Discord server: Join Here.
This article has been flagged for questionable relevance. Its connection to the systemic consumer protection issues outlined in the Mission statement and Moderator Guidelines isn't clear. Articles that focus on isolated incidents, personal disputes, or local matters may not meet the inclusion criteria for the Consumer Action Taskforce Wiki.
Articles in this wiki have to meet the following criteria:
- Systemic Nature: Demonstrate a broader pattern of systemic abuse, negligence, or policies that align with modern consumer exploitation (e.g., ownership revocation, barriers to repair, privacy violations, changing the terms of the sale after the sale).
- Relevance: Relate to consumer protection issues that extend beyond individual grievances or localized problems.
- Evidence: Provide verifiable evidence or credible sources to support the author's claims and demonstrate systemic impact.
Examples of articles that do not meet these criteria:
- A single negative customer experience; with no evidence of systemic issues or company policies enabling such behavior.
- Localized disputes, such as a bad experience with a contractor or small business, better suited for platforms like Yelp or local consumer protection agencies.
- Complaints that focus on personal dissatisfaction (e.g., "I waited too long for a response") without tying the issue to broader consumer exploitation themes.
To justify the relevance of this article:
- Provide evidence demonstrating how the issue reflects broader consumer exploitation (e.g., systemic patterns, recurring incidents, or related company policies).
- Link the problem to modern forms of consumer protection concerns, such as privacy violations, barriers to repair, or ownership rights.
- Add credible sources or documentation that substantiate claims and connect them to systemic practices. i.e:
- A company that takes 5 days too long to refund a deposit is a bad Yelp review. Not eligible for inclusion.
- A company with 500,000 active repairs at any given time that purposely delays all deposit refunds for a period of five days, in order to invest/gamble with these deposits on their balance sheet, with verifiable hard proof from internal communications that this was an intentional & standard practice performed with malicious intent is eligible for inclusion.
If you believe this notice has been placed in error, or once you have made the required improvements, please visit the #appeals
channel on our Discord server: Join Here.
End of Stub Notice. The article content begins below this line.
Since August 2024 i noticed that Chrome forces its own update by crashing windows10 (bluescreen) while playling YouTube videos.
Background[edit | edit source]
I have been doing electronics since the Apple ][ and the C-64. My whole life, I had no one to ask for information or help, as computing at home—and for most people at work—was completely new. So I think I can say that I know what I’m talking about because computers weren’t just my hobby; later, computers and electronics became my profession as well. I learned the most difficult and complex things, so everything else was and still is easy. With this in mind, you can understand why I believe the growing mass of truly dumb people is a problem—and that these problems will soon escalate dramatically, because holding a cellphone right does not make you intelligent. And yes, I have been coding since the Apple ][.
$2
[Incident][edit | edit source]
I have noticed that Chrome forces its own update by causing a Windows crash (bluescreen). The crash seems to be deliberately triggered to bypass update restrictions and ensure that Chrome updates itself upon reboot. This has been happening since August 2024.
I have several identical laptops, all running Windows 10, some with Chrome from November 2024. The ones where Windows Update and Chrome Update are disabled crash while watching YouTube videos. The laptops that receive updates do not crash. I even have made identical drives to test this.
At first, I thought this was because I had set Windows Update to pause for seven days. Then I tested completely disabling updates, and in all cases, Chrome crashes Windows to force its update. It’s as if Chrome says, *"You won’t update me? I’ll wait a few days… but then—"* You get the idea.
All Chrome versions since August 2024 behave this way, even though the updater is disabled—blocked by system permissions (`no execute, no read`) and even deleted. Windows Update is also disabled through the registry, preventing write and read access to specific files.
[Company]'s response[edit | edit source]
I did not tell google, they surely know...