Previous registry entry to accept all EULA no longer working

Article
2018-03-07

Question

_{Wednesday, March 7, 2018 7:48 PM}

We have been using the follow registry keys to auto-accept the EULA for our domain users, and avoid tutorial/welcome pop-ups. This was successful with previous versions of CTR Office 365 ProPlus when the EULA was a "First Things First" pop-up. After a recent CTR version update, users are being prompted with an "Office Is Almost Ready" EULA which is still present with the registry entry in place. If there an updated registry entry for the new prompt. I have also ensured "Disable First Run Movie" and "Disable Office First Run on application boot" are enabled in the Office 2016 GPO

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Lync
Value name	TutorialFeatureEnabled
Value type	REG_DWORD
Value data	0x0 (0)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Lync
Value name	IsBasicTutorialSeenByUser
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Lync
Value name	UserConsentedTelemetryUpload
Value type	REG_DWORD
Value data	0x0 (0)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\FirstRun
Value name	BootedRTM
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\FirstRun
Value name	disablemovie
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Common\General
Value name	shownfirstrunoptin
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Common\General
Value name	ShownFileFmtPrompt
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Common\PTWatson
Value name	PTWOptIn
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Common
Value name	qmenable
Value type	REG_DWORD
Value data	0x1 (1)

Hive	HKEY_CURRENT_USER
Key path	Software\Microsoft\Office\16.0\Registration
Value name	AcceptAllEulas
Value type	REG_DWORD
Value data	0x1 (1)

All replies (12)

_{Thursday, March 8, 2018 8:04 AM}

Hi Chris,

>> After a recent CTR version update, users are being prompted with an "Office Is Almost Ready" EULA which is still present with the registry entry in place.

Does this prompt appear during the process of installation or when the first time a user runs an Office application?
As per your concern about the recent change, could you please collect the detailed build number of Office 2016?

Besides, please have a check to see if the following GP has been configured to disabled:

User Settings --> Administrative Templates --> Office 2016 --> Privacy --> Trust Center --> "Disable opt-in wizard on first run"

Any update is appreciated.

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

_{Thursday, March 8, 2018 2:13 PM}

Current build being installed 16.0.9001.2138. In additional to the registry entries the follow GPOs are set as well. The EULA is present at first run, which we are trying to avoid in order to script a system setup process.

Microsoft Office 2016/First Run

Policy	Setting	Comment
If you enable this policy setting, the Office First Run does not run on first application boot. If you disable or do not configure this policy setting, the Office First Run about signing-in to Office comes up on first application boot if not previously viewed." gpmc_settingname="Disable Office First Run on application boot" gpmc_settingpath="User Configuration/Administrative Templates/Microsoft Office 2016/First Run" gpmc_supported="At least Windows 7 or Windows Server 2008 R2" href="javascript:void();">Disable Office First Run on application boot	Enabled

Microsoft Office
2016/Privacy/Trust Center

Policy	Setting	Comment
If you enable this policy setting, users have the opportunity to opt into participation in the CEIP the first time they run an Office application. If your organization has policies that govern the use of external resources such as the CEIP, allowing users to opt in to the program might cause them to violate these policies. If you disable this policy setting, Office 2016 users cannot participate in the Customer Experience Improvement Program. If you do not configure this policy setting, the behavior is the equivalent of setting the policy to "Enabled"." gpmc_settingname="Enable Customer Experience Improvement Program" gpmc_settingpath="User Configuration/Administrative Templates/Microsoft Office 2016/Privacy/Trust Center" gpmc_supported="At least Windows 7 or Windows Server 2008 R2" href="javascript:void();">Enable Customer Experience Improvement Program	Disabled

_{Friday, March 9, 2018 9:24 AM}

Hi Chris,

Did you include AcceptEULA="TRUE" in the configuration file if Office is installed with the user's account? (See this article.)?

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

_{Monday, March 12, 2018 1:48 PM}

The following is the configuration.xml file being provided when the package is provided to SCCM.<Configuration>

_{Tuesday, March 13, 2018 8:03 AM}

Hi Chris,

I did further test and noticed that the EULA prompt is related to the registry below:

**Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Registration\MACHINENAME\90160000-000F-0000-0000-0000000FF1CE}\O365ProPlusRetail\EULA
**

"16"="PLEASE NOTE: Your use of the subscription service and software is subject to the terms and conditions of the agreement you agreed to when you signed up for the subscription and by which you acquired a license for the software.

Please try adding the registry above and also enable the group policy "Disable opt-in wizard on first run" to see if it works in your side as well.

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

_{Monday, March 19, 2018 9:10 AM}

Hi Chris,

Just checked in to see if the information was helpful. Please let us know if you would like further assistance.

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

_{Friday, March 23, 2018 3:59 PM}

We're seeing the exact same issue here, I have followed all the steps recommended above, and the issue still exists.

_{Thursday, March 29, 2018 8:34 PM}

Registry entry was already present and "Disable opt-in wizard on first run" is configured, however still getting Sign-In request

_{Wednesday, April 18, 2018 11:41 AM | 1 vote}

Hi Yuki!

I am rolling out Office Professional Plus 2016 (volume license). With comparing registry excerpts before and after manually accepting the requester, I found out more or less the same what you posted.

In my case, the existence of the registry key

[HKCU\Software\Microsoft\Office\16.0\Registration\<machinename>\{90160000-0011-0000-0000-0000000FF1CE}\EULA]

with an empty REG_SZ value "8" was sufficient to suppress the requester.

Unfortunately, someone had the great idea to put the machine name in the registry key name. I really would like to know if that was necessary, as was to use a cryptic registry key name. For me that looks as if somebody forgot something in a beta version, or wanted to exacerbate us admins' work by forcing us to do extra detective work. The shortcomings of the concept "security by obscurity" should be widely known, so maybe one could see it as easter egg joke to put the product name "Office" into the key name in such a garbled way.

Having a machine name inside keynames in user hives of registry makes it really a pita to change machine names (which is sometimes necessary, and which is freqently done when giving a pre-installed machine to a new user - and no, we are not using AD for several reasons). You have to fix that in every existing user profile, lest everybody gets the requester again.

Additionally, I think it is not a really good idea to store chunks of text including several newlines in the registry, it just blows it up and slows it down. Even more so since the value is not even checked, it works also if it is left empty.

Maybe you could rely these thoughts back to whoever invented this new key.

Regards, Norman.

_{Thursday, April 26, 2018 8:38 AM}

Hi,

I created a .bat to write this reg string using %computername%, this worked creating the reg entry but it hasn't suppressed the EULA. Any ideas?

Thanks,

David

UPDATE:

Scratch that... Added the "Disable opt-in wizard on first run" to the same GPO as the logon script above, all OK now. Very Happy. Thanks to all involved.

_{Thursday, February 21, 2019 2:19 PM | 1 vote}

I was able to remove "The fine print" pop up by setting two keys:

HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Licensing

REG_SZ

EulasSetAccepted

16,0,

HKCU\SOFTWARE\Microsoft\Office\16.0\Common\General\

DWORD

ShownFirstRunOptin

_{Friday, November 29, 2019 6:27 PM}

Thank you. I was getting the popup at every launch (after I changed the pc name).

I updated the reg entry above to the new pc name, and the eula is gone.

It still had the old pc name listed.

Share via

Previous registry entry to accept all EULA no longer working

Question

All replies (12)

Additional resources