From the default Google Chrome 67 user profile on Windows 10
C:\Users\sam\AppData\Local\Google\Chrome\User Data\Default
What are the MINIMAL files/folders to backup to get back ONLY:
Chrome settings
User Bookmarks
User Cookies
User Extensions and their settings
after copying those files/folders in an empty folder (same or other PC):
C:\Users\sam\AppData\Local\Google\Chrome\User Data\User2
and starting
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --Profile-DiRECTORY="User2"
This list works fine sometime but sometime not (folder name ending by backslash):
data_reduction_proxy_leveldb\
databases\
Extension Rules\
Extension State\
Extensions\
IndexedDB\
Local Extension Settings\
Local Storage\
Managed Extension Settings\
Service Worker\
Session Storage\
Sync Extension Settings\
Web Applications\
Bookmarks
Cookies
Current Session
Extension Cookies
Favicons
Google Profile.ico
Last Session
Login Data
Network Action Predictor
Network Persistent State
Origin Bound Certs
Preferences
QuotaManager
Secure Preferences
Shortcuts
Top Sites
TransportSecurity
Web Data
My extensions:
PageChopper
Adblock Plus
Tampermonkey
Auto-Translate
Stylish - Custom themes for any website
Selection Search
Extensions Manager (aka Switcher)
Flashcontrol
Clickable Links
SmoothScroll
MultiHighlighter
Session Buddy
Related
I just upgraded to Google Chrome v73.0.3683.103 and I am now unable to view FTP sites in Chrome. Instead of Chrome loading the FTP directory listing in the browser, it downloads a file named download which contains a directory listing.
How do I get the ability to view the FTP directories directly in Chrome back?
I have tried going into Internet Options > Advanced and clicking on the "Enable FTP folder view (outside of Internet Explorer)" but, that didn't seem to do the trick.
In-browser FTP was deprecated back in v72. I hadn't updated Chrome in a few releases. I have rolled back to v71 until I find a better workflow substitute
DETAILS: https://developers.google.com/web/updates/2018/12/chrome-72-deps-rems
I publish my extension in google web store and install it successfully in my chrome.
So I find extension's files in this directory:
C:\Users\User_Name\AppData\Local\Google\Chrome\User Data\Default\Extensions.
I use my extension for native messaging in chrome.
How do I get .crx file for publish my extension for other people without internet connections?
Or exactly like firefox *.xpi files.
Also:
If I pack extension's files in above DIR to zip and rename to crx file, and drop down to chrome this error occurs:
Package is invalid: CRX_HEADER_INVALID.
Packaging
Extensions and themes are served as .crx files. When uploading through the Chrome Developer Dashboard , the dashboard creates the .crx file automatically. If published on a personal server, the .crx file will need to be created locally or downloaded from the Chrome Web Store.
Download .crx from the Chrome Web Store
If an extension is hosted on the Chrome Web Store, the .crx file can be downloaded from the Developer Dashboard. Locate the extension under "Your Listings" and click on "More info". In the popup window, click the blue main.crx link to download it.
The downloaded file can be hosted on a personal server. This is the most secure way to host an extension locally as the contents of the extension will be signed by the Chrome Web Store. This helps detect potential attacks and tampering.
Create .crx locally
Extension directories are converted to .crx files at the Extensions Management Page. Navigate to chrome://extensions/ in the ominibox, or click on the Chrome menu, hover over "More Tools" then select "Extensions".
On the Extensions Management Page, enable Developer Mode by clicking the toggle switch next to Developer mode. Then select the PACK EXTENSION button.
Specify the path to the extension’s folder in the Extension root directory field then click the PACK EXTENSION button. Ignore the Private key field for a first-time package.
Chrome will create two files, a .crx file and a .pem file, which contains the extension’s private key.
Do not lose the private key! Keep the .pem file in a secret and secure place; it will be needed to update the extension.
Learn More
This is updated dashboard in order to download your crx file
I try to auto-install a chrome extension on a WIN10 device that have no connection to the internet and thus can not access the Chrome Web Store. So uploading the extension to the CWS is no option. The extension exists as a crx file on a server in a network and on the device.
On Chrome Versions 59 and lower I could install the extension via settings in the registry. When Chrome was started, the user was ask if he wants to install the extension.
For this I used the registry key ExtensionInstallWhitelist and defined the path and version of the extension under the key "[...]/Google/Chrome/Extensions/[ExtensionID]".
But since Version 60 the extension does not appear in Chrome anymore. So I tried to auto-install the extension via an Active Directory domain policy.
I have imported the chrome policy templates and configured the entry ExtensionInstallForcelist (http://www.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist) in the group policy editor. This policy setting is listed on the chrome://policy page in Chrome. But the extension does not appear in Chrome. The ExtensionInstallForcelist entry contains "[ExtensionID];[url where the crx file resides]". I also tested this with an url to an "Update Manifest XML document" which points to the crx file. Neither of them worked.
Does anyone know, if Chrome 60+ still supports this?
Is my configuration incorrect?
Any help will be appreciated, thanks!
I'm developing an extension and I'm trying to use the enterprise.deviceAttributes API, but "This API is only for extensions pre-installed by policy.". How can I simulate a pre-installed by policy extension in sandbox so I can develop it?
Also, I noticed that this API is not "dev channel only" anymore, so now I can use it in production?
Question about Google Admin:
I will require the users to install my extension to their "children"* via Google Admin > Chrome Management > User Settings, so the user won't need to enroll devices, and the extension will be "installed by policy".
In this case, which devices aren't enrolled, can I still get the deviceID of the "children" with my extension and then call the Admin API to get device info?
*Children is an example, could be students, employees....
I found a workflow that doesn't require me to wait on approval from the Chrome Web Store, but it's a little clunky.
This was tried on a Chromebook in developer mode. I don't know if that matters.
Upload your extension as a draft to the Chrome Web Store
Note the ID assigned to your draft in the Chrome Web Store developer dashboard
In Google Admin, under Devices > Chrome > Apps & Extensions select "Add Chrome app or extension by ID"
Put in the extension ID from the developer dashboard
Change "From the Chrome Web Store" to "From a custom URL" and put in a junk URL
Make sure the extension is set to "Available" and not "Forced" (if it is set to forced you won't be able to manually install the extension)
Download the CRX file from the "package" section of your saved draft from the chrome web store and copy it to your Chromebook. Your CRX file will now be signed by the blessed Google keys
Drag it in to the chrome://extensions page on the Chromebook to install it
Disable the extension but do not uninstall it
Change the extension to "forced" in Google Admin
Go to chrome://policy and reload policies.
If you refresh chrome://extensions you should see that the extension is now force-enabled and should be running with enterprise.deviceAttributes permissions (assuming your extension requested them)
I have my own extension which I want to install without user interaction. I packed it into a .crx file and entered these values in the registry:
HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\Extensions\[ID]
"version"="1.0"
"path"="[crx Path]"
I tried both current user and local machine without success.
This was working before. My extension can be installed by using developer mode and dragging and dropping the crx file into chrome extensions. But I want to install without user interaction.
Is registry installation not allowed anymore?
even though you create a registry entry, Chrome will not use the local crx file for installation.
you need to supply: update_url with string value set to "https://clients2.google.com/service/update2/crx".
Upon chrome launch, Google will fetch the extension from web-store and show notification that'd let user install the extension.
Back in old days you'd side-load extensions. Those days are long gone.
Now you need to publish extension in webstore, and point update_url to store.
There are some exceptions (specifically for enterprise users with group policy settings) as mentioned in comments.