Able to reproduce the issue on Skytap tap Environment "Windows GPO Testing - Stable - K"

This behavior is expected when "Incognito mode availability" policy is enabled, please disable this policy and let us know your observations also provide us the "chrome://policy" screenshot.

Thank You... 

Thanks for the response.  This wasn't the expected behavior two months ago.  Why did this change?  I know turning off incognito mode by group policy will fix this issue, but we want to keep it on.  I have attached the policy screenshot.

Deleted: Policies.pdf 60.4 KB

Policies.pdf 60.4 KB Download

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Just to Update,

Tested the scenario with the old chrome stable version #57.0.2987.113, observed the "Incognito mode availability" policy is behaving as expected.

"Incognito Mode Availability" has 3 options :

1. Incognito Mode Available :  We can see the Incognito Mode available in Wrench Menu
2. Incognito Mode Disabled  :  We can't see the Incognito Mode available in Wrench Menu
3. Incognito Mode Forced    :  On launching chrome, we see chrome incognito window 


Thank You...

Please try with an older version.  Perhaps 54.  This issue just started in the past few months.

Just to update,

As per comment #7 tested this issue on Windows 10 chrome #54.0.2840.0, still seeing the same behavior as mentioned in comment #5

Attaching the screen-cast for reference.

Deleted: Issue 722843-1.mp4 1.2 MB

	Issue 722843-1.mp4 1.2 MB View Download

From your Chrome://policy you are not setting a home page through gpo.  We do.  Next week I will attempt to attach a video of the behavior I described in the inital report.

Thanks for the update.I don't see any home page set from the attached chrome://policy.Looks like by Home Page you meant Session restore? 

I tried with the following policies set, which is similar to the one you attached.

Set Policies
============

Incognito mode availability - "incognito mode is forced"
Startup pages - "Enabled", select any option

By launching chrome, the incognito window is opened, which is expected.
If you make "Incognito mode available" then users will have incognito mode enabled plus have the browser open directly to Startup pages.

Unfortunately we cannot downgrade our test setup to older versions.Please try the above and let us know the behavior.

Deleted: Capture.JPG 186 KB

	Capture.JPG 186 KB View Download

I can verify that this problem exists, is new and is causing me problems as a system admin.  Please fix it so it works like it used to.

Unable to reproduce the issue on reported version & latest stable-66.0.3359.181 .Please check the issue on windows using latest chrome version-66.0.3359.181 & let us know your update on the same.

Thanks..!

This looks like a request for Incognito + home page.

It is more a regression from my reading of the description than a new feature request. IT seems that we broke how we load startup pages if incognito is enforced. We should simply make sure our policy startup code is compatible with incognito mode. 

This behavior still persists in V70.  We've worked around it by putting the homepage URL in the windows shortcuts we provide but a fix would still be fantastic.  Screenshot showing both HomepageLocation and IncognitoModeAvailability=2 policies from a V70 install.

Deleted: ChromeIncognitoHomepageBroken.png 209 KB

	ChromeIncognitoHomepageBroken.png 209 KB View Download