Mydefault browser is chrome. Clicking on any hyperlink in a spreadsheet opens chrome. This is not so for LibreOffice offline help. Pressing F1 opens in the Edge browser.
This would not be serious if it was not for the search box which does nothing in edge.
Copying the link into chrome and all works.
So, why does F1 use Edge as it is not the default brower?
I am using Windows 10 64 bit. LibreOffice is 6.2.0.3 x64
Google only provides an online setup file for Google Chrome which installs the latest version of Google Chrome. It happens frequently that a user upgrades to a new version of Google Chrome and gets upset by an unpleasant feature, a missing option or an annoying bug. Therefore, some users want to roll back to an older version of Google Chrome to preserve a useful feature, option or support some legacy technology. However, is it really wise to use an out-dated verison of Google Chrome? The answer is NO since out-dated browsers usually come with security issues. A better solution to the problem is to use Slimjet browser, which runs on the latest Blink engine while offering more flexibity, features and options compared with Google Chrome. With Slimjet, we give users more choices to tune their browser to their own personal preference instead of forcing a majority style on everyone. Slimjet also integrates more features internally in the most efficient way so that you don't have to spend time dealing with unstable and resource-consuming third-party plugins. Best of all, Slimjet syncs all your Chrome data and settings via your Google account and is compatible with your favorite Chrome extensions. There is absolutely no learning curve for you to switch from Chrome to Slimjet. Give Slimjet a try now and you will never look back!
For users who insist on using an old version of Google Chrome and becoming vulnerable to security issues, you can find the right version of Google Chrome to download for your platform in the following sections.
Unfortunately, we only started to archive old versions of Chrome since Chrome 48. Chrome dropped support for Java, silverlight and other NPAPI plugins in Chrome 45. If you are looking for an old version of Chrome with support of Java, silverlight or other NPAPI plugins, you would have to use Slimjet Web Browser, which is based on Chromium and retains support of Java, silverlight and other NPAPI plugins.
The old versions of Chrome before V58 are packed as 7zip self-extracting executable. Just run the executable and extract the files under any folder on your hard drive. Then launch Google chrome with chrome.exe under the extraction folder. After V59, the archived chrome old version files are official Chrome offline installers. Just uninstall any current version of Chrome first and then run the downloaded installer. It's a one-click installer without any interactive UI.
Please notice that Chrome dropped support of XP and Vista since Chrome 50. If you are using XP and Vista, please download Chrome 49 or earlier, or download Slimjet Web Browser, which is based on Chromium and continues to support XP and Vista.
Note: Google Chrome stopped release 32-bit builds for linux since Chrome 49. If you are still using 32-bit linux and would like to be protected with the latest security patches as well, you can use Slimjet Web Browser, which is based the Chromium open source project and continues to support 32-bit linux.
Sometimes it can be just because you don't like a new update or the new version of your preferred browser. Different people have different reasons, for example, developers don't like the placement of tools and in other cases the favorite extensions might not appear so useful. In such circumstances, all you need is the same previous version. In case of Chrome, though Google doesn't provide you with any Source) to download older versions of Google Chrome, but if you are really comfortable with those you don't need to disappoint. Slimjet offers you all older version under one roof.
Google do not support any rollback to the previous versions of Chrome. But that doesn't mean, you cannot get the one. Yes, there is a simple way out to get previous version. Just uninstall your present adaptation, erasing each user's saved profile information, and then re-install the needed version. Here it is important to note that user may lose their bookmarks, history, and so on. Hence, be careful while you proceed with the same.
Now getting and downloading the prior versions of Google Chrome is possible. Slimjet share the old versions of Chrome, packed as 7zip self-extracting executable file. Download the one you need, run the executable and extract the files on your hard drive. Simply launch Google chrome with chrome.exe under the extraction folder. You can scroll above for different versions, available in 32- bit and 64- bit.
Google provides the essential tools to deploy Chrome Browser for your enterprise. Google also provides instructions, recommendations, and critical considerations for deploying Chrome Browser in an enterprise environment.
The admin tools by the Google team allow administrators to configure, package, and deploy Chrome Browser at the system level. You can also manage policies on an ongoing basis. You can download the latest Chrome browser deployment guide for free. The guide is published by Google and is useful for Windows administrators who want to deploy the Chrome browser to their organization.
This Chrome browser deployment guide will cover the steps to download, package, and deploy Google Chrome enterprise with ConfigMgr. The guide uses the Windows Installer (MSI) version of Chrome Browser for enterprise for deployment, which is available for Windows 10 and Windows 11.
Since most of the organizations use Windows 10/11 OS, it is recommended you download the Windows 64-bit version of chrome. In case your organization has a mix of 32-bit and 64-bit computers, download both the chrome 64-bit and 32-bit offline installers and package it in SCCM. For your information, when you download Google Chrome enterprise installer, the package includes the following.
Save the googlechromestandaloneenterprise64.msi to a folder where SCCM can access it. You may also download the icon or logo for Google Chrome. We will assign this logo to the app while creating the application in SCCM, and it will appear in Software Center along with the application for users.
On the General page, specify the settings for Google Chrome application. Select Automatically detect information about this application from installation files. Select Type as Windows Installer (*.msi file) and specify the location of Google Chrome .msi file. Click Next.
The advantage of MSI installers is that SCCM can read the information from the file and import it without any hassle. The following information is imported by SCCM from the Google Chrome enterprise MSI installer.
This is an optional configuration step where you specify the logo for the Google Chrome application so that it is visible for users in Software Center. Specifying an icon also makes it easy to locate the applications in the software center.
In this step, we will ensure the Chrome browser application content is distributed to SCCM distribution points. The application content has to be distributed to all the distribution points before you perform the chrome deployment. In the ConfigMgr console, right-click on the Google Chrome application and select Distribute Content.
On the Completion window, click Close. The Configuration Manager will now distribute the chrome application content to the selected distribution point servers. You can monitor the application distribution status in the Monitoring workspace of the Configuration Manager console. Learn how you can use right click tools to monitor content distribution in SCCM.
On the Content page, click Add button and specify the distribution points to which you would like to distribute the Chrome browser application content. You may also select distribution point groups. Since we have already distributed the content to distribution points in our previous step, click Next.
On the Scheduling window, you get the option to schedule or make this app available at specific time. If not the application will be made available as soon as possible to client computers. Click Next.
The Chrome enterprise application is now distributed to the DP, and the client machines should now have the application listed in the Software Center. This completes the steps for Google Chrome deployment using SCCM. The Chrome application is now visible under the Applications node of the ConfigMgr console.
In this section, we will verify if the Google Chrome Enterprise application installs fine on the client computers. Log in to a client computer, and launch the Software center. Click on the Applications tab and select the Google Chrome Enterprise application and click Install.
The Google Chrome browser application is now downloaded from the local distribution point server for installation. You can review the Chrome application installation progress using AppEnforce.log using the CMtrace log tool. To know the location of this file and other files, refer to the SCCM Log files.
Matched exit code 0 to a Success entry in the exit codes table confirms that the Google Chrome application has been installed successfully. The Google Chrome enterprise application installation is successful.
I am sure by now, you know that to deploy Chrome browser using ConfigMgr is easy. Chrome checks for new updates regularly, and when an update is available, Chrome applies it automatically when you close and reopen the browser.
Manually updating the Chrome browser is not a solution for large organizations. Moreover, not all users are aware of the steps to update the Chrome browser when there is a zero-day patch released for Chrome.
3a8082e126