How do we disable CONSTANT notifications that "To get future Google Chrome updates, you'll need Windows 10 or later. This computer is using Windows 8.1."
There are a million reasons why certain machines will *never* get updated from Windows 8.1.
The last version of Google Chrome without this nag is 107.0.5304.122.
Sadly, the solution does not appear to work on Portable Chrome, only full install Google Chrome.
Can this be incorporated into the Portable version of Google Chrome:
SOLUTION: Make this text file with a .reg extension then double click on it, to enter it into registry, restart Google Chrome:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Google\Chrome]
"SuppressUnsupportedOSWarning"=dword:00000001
I'll likely incorporate this into the legacy Windows 7/8/8.1 release of Chrome Portable. Not sure I'll do it before then as it'll be moot in 54 days when support for these outdated versions of Windows is dropped by Google Chrome and other Chrome-based browsers. Users should be seeing this as they're on a countdown to remain secure by either migrating to Firefox or updating Windows.
There doesn't appear to be a simple manual fix for advanced users like passing a command line parameter like you can to disable the 'can't update' warning: https://portableapps.com/comment/252088#comment-252088
Sometimes, the impossible can become possible, if you're awesome!
I was told that "it works if you add the paths google and chrome"
What do those words mean, how can "paths" be added to incorporate the above posted fix into the portable version?
We understand that the last Windows 7/8 version will be Chrome 109, but why not add those paths, if that's a thing, to versions 107 and 108, right now?
Back in a day artificial OS limitations could be removed, so a very important question:
if Chrome 110 will not work under Win 7/8, is there a way to force-run it on Win 7/8 anyway, knowing the stability risks may be there?
Compatibility mode?
It's not an artificial limit or Google deciding they're just not testing under Win 7/8/8.1 anymore. Chrome 110 outright crashes on Windows 7/8/8.1 because the Windows kernel doesn't support the features that the new compiler is using: https://imgur.com/N0bIolu
I don't know what you're referring to with "it works if you add the paths google and chrome". I didn't say that nor did anyone else in this thread.
A single warning on startup seems reasonable to me though it may not to you. I have to find time to update the Google Chrome Portable launcher to handle moving that key into and out of the registry. I have other things that are more pressing time wise.
Sometimes, the impossible can become possible, if you're awesome!
P.S. (Very) respectfully:
Users absolutely should *not* "be seeing this" NAG repeatedly.
To remove nag bar possible use parameter to disable all bars:
Thank you for posting.
For people who have never modified Portable Apps, where and how is that line entered into Chrome Portable?
As the legacy version has been released, would it be possible to add the SuppressUnsupportedOSWarning entry to user's registry at startup of the application and remove at its shutdown?
You must have admin rights to add it to the registry as it is within the Policies key. I added a .reg file to GoogleChromePortable\Other\Source that you can double-click to add it. You can not do this any other way. This is by design of the Chrome team.
Sometimes, the impossible can become possible, if you're awesome!
Thank you. This is a big deal. Thank you.
Is the final version for Windows 7/8 only available in 32-Bit, what is the link to the 64-Bit version with this fix?
If you upgrade via the platform, both the 32-bit and 64-bit releases will create a legacy version. Both are available for direct download from the platform (though 64-bit requires having Advanced Apps visible in Options). Both are available from their respective homepages within the Details section at the bottom of the page. https://portableapps.com/apps/internet/google-chrome-portable-64#downloa...
Sometimes, the impossible can become possible, if you're awesome!
Hmmm. I still get this for both 32-Bit and 64-Bit:
To get future Google Chrome updates. you'll need Windows 10 or later. This computer is using Windows 8.1.
Every time I start the Legacy version 109 with registry entry imported under a full Administrator account.
I have screnshots of both the nag and registry entry, anyone else experiencing problems?
Add the registry key from Other\Source. Do NOT run Google Chrome Portable as admin. It's hugely risky security-wise and will remove the customization you just did with that .reg file I mentioned.
Sometimes, the impossible can become possible, if you're awesome!
Per your suggestion, I logged out of the Administrator account, logged into a regular user account, and it worked!
Since your post is not a suggestion, it appears that the fix does not work under Administrator accounts
Is this a matter of choice? To protect us? Mine is a case where I actually almost never use Chrome, I use Firefox.
If I used Chrome, I would install it, and there already is a fix for installed Chrome.
I only use Chrome rarely on the Admin system, which is reimaged frequently anyway, but the point is Portable version is being used - so is it possible to replicate the fix to Portable Chrome so that Portable Chrome does not display the nag, just like Installed Chrome does not, even on Admin systems, when fixed?
Could you post what it is or have another reg with warnings, so that people can choose to fix Portable Chrome, which, I mean, they are already using an old and now vulnerable Chrome version, I mean plus... a year or two from now, it's not like they can update Chrome, so protecting us from risk, in a situation where we are using both a no longer updated OS as well as a no longer updated browser... it does not make sense.
Unless of course, it's impossible to run the fix on an Admin account, is it impossible?
You can be on an admin account without issue. But if you run as admin, it'll replace the Policies key and subkeys. I've tested this on a clean Win7 VM and it works on an admin account as I stated above. If you disabled UAC or something like that, that would likely bork it.
Sometimes, the impossible can become possible, if you're awesome!
Of course UAC is disabled. Absolutely 100% disabled.
The very first thing to do when installing Windows on non-important systems is to disabling the UAC nag.
The very nature of this fix is to disable a similar nag.
However, re-enabling UAC all the way up, still does not make this fix work on Admin systems.
So something else makes the fix not work on Admin systems.
Real Admin system in this conversation is defined as:
* You may enable the hidden actual Administrator Account so that you can have ultimate Administrator privileges that surpass privileges that user accounts 'with Administrator Privileges' have.
Start > type in: Command Prompt
Right click on Command Prompt > Run as administrator >
net user administrator /active:yes
Press Enter > Start > Click on your user name and Sign out.
Now click anywhere to see the newly enabled real Administrator account in the lower left corner > click on it and sign in.
That's why, then. UAC off or using the admin account you mention means the launcher has access to HCKU\Policies (which it shouldn't) so it's backing it up and restoring it. A standard user or admin account doesn't have access to those keys without "Run as Admin". I've tested it on unaltered Win7 and it works as expected.
You can either modify the permissions on the specific Google Chrome policies key to prevent it from being altered by the launcher. Or you can download the GoogleChromePortableLauncher_2.3.7.0-Mod.7z modded launcher I just did that ignores HCKU Policies and see if that works. Just grab the GoogleChromePortable.exe out of the 7z and replace your existing one. Please note that I won't be supporting this mod. You're welcome to tinker with it further.
Sometimes, the impossible can become possible, if you're awesome!
Haha - yhea - it works!
To anyone else reading this, simply download GoogleChromePortableLauncher_2.3.7.0-Mod.7z
[The file with -MOD at the end of the file name] from
https://sourceforge.net/projects/portableapps/files/Source/Google%20Chrome/
and copy-paste extracted contents into your Google Chrome Portable folder, overwriting existing files. It all works after that.
Thank you also for pointing out earlier in the thread how to disable the red 'can't update' warning.
Even though no one asked, you actually posted that including a link to a fix, and it was a great fix for an *extremely* annoying nag, that I never got around to figuring out how to disable, but thanks to you, another excellent fix! Thank you very much.
So, I updated portable Chrome on an 8.1 PC that will not be upgraded because of Windows Media Center. Is there a way to simply rollback or downgrade to the previous version so I don't need to bother with setting up a legacy version largely from scratch? Thanks!