Should GCPW (Google Credential Provider) automatically log me into Chrome Browser?

[lorzeni]

Hello, any news about the issue? From 2 week ago i can't get auto login in chome with GCPW, this worked before. What is the best way to let google know the problem?

[rogerdnixon]

Yes - Google have identified that this has been caused by a recent Chrome update and are looking for a fix. You should have had an update if you logged a support ticket with Google.

 

My ticket update states:

Our product team shared that the issue you are facing was caused by changes in the chrome browser.

They also informed us that they are working on a fix.

I will keep you posted in case of any advance, please expect more information from us in no later than the next 4 business days (Tuesday March 25th before 6 PM  CST).

[lorzeni]

48 minutes ago, rogerdnixon said:

Yes - Google have identified that this has been caused by a recent Chrome update and are looking for a fix. You should have had an update if you logged a support ticket with Google.

What's the best way to open a ticket?

[whartomt01]

https://support.cloud.google.com/portal/cases

 

Similar response for my ticket

 

Quote

Thank you for your patience.

We have received an update from our higher-level support team regarding the ticket we created for you.

They have confirmed that the issue you reported is a known issue and is already being worked on. While the team has not provided an estimated time of resolution yet, we will keep you updated as soon as we receive any news.

 

[paulkerton]

Funnily enough, my ticket was closed but I have been given the internal ticket number for this #396696524
I've reopened our case. 

[lorzeni]

Opened a ticket 2 weeks ago and still not having replies. Any news from you?

[rogerdnixon]

Being fixed in Chrome 136. So month and a half give or take. 

[MathiasM]

18 hours ago, rogerdnixon said:

Being fixed in Chrome 136. So month and a half give or take. 

Isn't the release date for Chrome 136 planned for 29 april? So less than a month.

[rogerdnixon]

Maybe - we shall see - hence the "give or take". End of April would be nice.....

[MattCab]

On 02/04/2025 at 16:22, rogerdnixon said:

Being fixed in Chrome 136. So month and a half give or take. 

 

Hi,  We have had a several support tickets in with this issue from many of our local offices in our org.  Did you get confirmation of the fix from Google direct from your support ticket or is it on a changelog/bug fix list on a web site?  🙂

 

Thanks. 

[rogerdnixon]

Our ticket said fixed in Chrome 136. So the next release now.

[MattCab]

1 minute ago, rogerdnixon said:

Our ticket said fixed in Chrome 136. So the next release now.

 

We couldn't get them to ackowledge that the issue was a thing and I used this website as evidence.  They still wanted some gemini generated AI support suggestions that didn't make sense to finding or solving the problem.  At least you have it in writing 🙂.  

[MathiasM]

Hi everybody. I have just updated to Chrome 136 and can confirm this bug is fixed.

[paulkerton]

I just came on to say the same thing. I've just updated a machine to 136, and this is now fixed for us too.
 

2 hours ago, MathiasM said:

Hi everybody. I have just updated to Chrome 136 and can confirm this bug is fixed.

 

[mrstrong]

Slightly off topic but does anybody stick with the LTS releases (currently on 132) of chrome to mitigate this kind of thing ?

 

I was considering it for our managed Chromebooks.

[paulkerton]

53 minutes ago, mrstrong said:

Slightly off topic but does anybody stick with the LTS releases (currently on 132) of chrome to mitigate this kind of thing ?

 

I was considering it for our managed Chromebooks.

 

Its the battle of mitigation vs instant gratification of features.

[dhicks]

On 28/02/2025 at 10:35, TwistedHelixis said:

just logged in to Windows using GCPW and my yubikey key as the 2 step.

 

Resurrecting an older thread here - just got around to trying this, still no luck. Downloaded latest available version of GCPW, tried on a test machine and as soon as I've put my Google username and password in it skips straight past the "insert your USB key" to "There was an error - try another way".

[paulkerton]

6 minutes ago, dhicks said:

 

Resurrecting an older thread here - just got around to trying this, still no luck. Downloaded latest available version of GCPW, tried on a test machine and as soon as I've put my Google username and password in it skips straight past the "insert your USB key" to "There was an error - try another way".

Yubikey being unavailable with GCPW is a restriction of Windows. Google is working on it with Microsoft, I'm told.

Edited July 15, 2025 by paulkerton

[TwistedHelixis]

Yubikey being unavailable with GCPW is a restriction of Windows. Google is working on it with Microsoft, I'm told.

 

Worked for me last time I tested. I tested my Yubi key, txt pin and authenticor pin to log into Windows GCPW

Edited July 15, 2025 by TwistedHelixis

[TwistedHelixis]

When I get a bit of time ill do another test.

[TwistedHelixis]

Whats a good way to force it to ask me for 2 step again?

[whartomt01]

Sorry to open an old thread.

 

Anyone using GCPW. Do you have Windows GPO set - Browser sign in setting ' Force Users...' or 'Enable browser sign in'.

 

Enable works fine. But when forcing users to sign in, I'm getting the double sign in again (Windows first, then chrome). I really need to force users to sign in.

 

Anyone having the same. Or willing to share policies you have set

[TwistedHelixis]

We don't use any GPO settings with our GCPW systems. I always had issues trying to get it working with domain accounts. Worked perfectly when I removed the devices from the domain, although that was ages ago now and I know another school using domain devices without issue.

 

Did you manage to workout your issue?

 

At our site, when a user signs in to GCPW they are automatically signed in to Chrome, but they do still need to run through a few screens after opening Chrome for the first time.

Edited May 30 by TwistedHelixis

[whartomt01]

Still the same unfortunately. Works fine when 'Allow Sign in' is set. auto signs after clicking the usual first run screens.

But have an issue of students cancelling the first run boxes, and not signing in, they can then downloading extensions (VPN).

The setting to 'Force' sign in. Which you can apply from GPO or managed browser setting (Tried both). Works, but seems to force double sign in like people were previously experiencing.

 

[DGardiner]

54 minutes ago, whartomt01 said:

Still the same unfortunately. Works fine when 'Allow Sign in' is set. auto signs after clicking the usual first run screens.

But have an issue of students cancelling the first run boxes, and not signing in, they can then downloading extensions (VPN).

The setting to 'Force' sign in. Which you can apply from GPO or managed browser setting (Tried both). Works, but seems to force double sign in like people were previously experiencing.

 

 

setup chrome managed browsers to stop this - its only a registry entry, key for the base ou to place the browser