Windows 10 Version 1703 Extension
Cdztattoo Barreto
Hi @VipulSparsh-MSFT and @Walker McAninch , I managed after some lengthy testing, to get to the bottom of the problem for us. I did try older versions of Windows 10 (1903 etc.) and this wasn't the issue. We use Chrome CIS Level 1 security benchmarks that use ADMX ingestion (Chrome ADMX). One of those policies (which is now deprecated by Google) - NativeMessagingBlacklist with a wildcard (*) blocks access to the Native Messaging API's. You can either add in NativeMessagingWhitelist with your exceptions or use the newer Chrome policy of NativeMessagingBlocklist. This policy was the problem though.
windows 10 version 1703 extension
EDIT: Please note that the above NativeMessagingBlocklist and NativeMessagingAllowlist are only supported in Chrome 86 and onwards. To use the legacy policies, add the following Blacklist and Whitelist in:
The important value is the com.microsoft.browsercore value above. Be careful when copying and pasting the "Value" data above in respect of the speech marks ("") as if they are wrong, you'll get a remediation error within Intune.
I am having this same issue but do not have either policy set, the only policy I set is to force install the W10 Accounts app. We had this issue in 1909 and 2004, do you have any other info that may help ?
@RDW Thanks for reaching out. If you have already confirm that you have added the Windows 10 extension to Google Chrome, please verify if you see this registry in your machine. If not, then please create it :
If the registry value exists, then Intune and the MDM management channel have done their job. It's up to Chrome to enforce whatever the value/setting is supposed to do and outside of Microsoft or Intune's control.
@RDW I wanted to follow up and know if the above response helped in answering your query. If it did, please do let us know so that we can help you further. Also, please do not forget to accept the response as Answer; if the above response helped in answering your query.
i'm experiencing the same issue on 2004. works fine on 1909, but 2004 machines throw the "Chrome extension is not supported on your version of Windows. You must be on Windows 10 version 1703 or above." error.
An additional finding for this issue - if you happen to block CMD.exe for standard users (via AppLocker or another method) then the Windows 10 accounts extension will not work, as it appears to call CMD.exe to be able to read the device ID to then allow the conditional access check in AAD.
Hi everybody, two days ago I updated the OS with this release of windows 10 home: version 1703, Build SO 15063.483. The process was very very long. Today I tried to use Inventor 2017 but there was a problem with MSVCP110.dll. I followed the instruction found on Autodesk and I reinstalled Microsoft Visual C++. Now, when I run the program, I only see the first picture for 2 or 3 seconds but than nothing happen and the picture disappear. Somebody know if there is a alternative solution to the complete reinstallation of Inventor?
Many thanks.
Maurizio
Good morning,
thank you for your tips. I tried to use the option "repair" but it doesn't changed the situation. I reinstalled Microsoft C++ latest version and removed whole software Inventor. With a new installation the problem is solved but when I see a new windows updat, I am alvays scared.....
We are currently working to implement the Microsoft Teams integration for Genesys Cloud, but have run into an issue when attempting to sign into the embedded Teams client (necessary to show Teams presence within Genesys Cloud). When running Genesys Cloud in a web browser, like Microsoft Edge or Google Chrome, we are able to sign into the embedded Teams client within Genesys Cloud successfully. However, when using the Genesys desktop app, we receive an error:
"This application contains sensitive information and can only be accessed from:
Devices or client applications that meet Amica management compliance policy.
Since you're using Chrome, you need to install this extension. You must be on Windows 10 version 1703 and above. Alternatively, you can use Microsoft Edge or Internet Explorer to access this application."
The mentioned Chrome extension has already been installed to Google Chrome itself with no change in behavior for the desktop client. In looking at the internal Conditional Access policy that is blocking this request, it looks like the Genesys Desktop client is sending the Device as "Unknown" and we have a rule to block Unknown devices that we cannot remove.
In order for Teams presence to sync, the users are required to sign into the Teams app, and our org primarily uses the desktop app. Any thoughts on why specifically only the desktop app isn't able to sign into the Teams integration and what might be done to resolve this?
HI there, I believe you're hitting an issue with the desktop client itself and not necessarily the Teams integration. The issue is around the conditional access policies as you mentioned and how the desktop client - written in CEF - supports (in this case doesn't support) this.
Thanks very much for the information and the idea link! I'm disappointed to know that we won't be able to use the Teams integration for presence with the desktop client, but I very much appreciate the info!
Windows 10 Creators Update[1] (also known as version 1703 and codenamed "Redstone 2") is the third major update to Windows 10 and the second in a series of updates under the Redstone codenames.[2] It carries the build number 10.0.15063.
The first preview was released to Insiders on August 11, 2016. The final release was made available to Windows Insiders on March 20, 2017, followed by a public release on April 5 via Update Assistant, and began to roll out on April 11.[3]
The update has reached end of service on October 9, 2018 in the Semi-Annual Channel.[4] The Enterprise and Education editions have reached end of service on October 8, 2019.[5][6] Support of this update on Surface Hub devices was available until March 16, 2021.[7]
I tryed to install Windows Development Kit on Visual Studio Community 2015, but it do not install correctly the software. Afther setup i don't find "driver" between visual studio's menu.I tried to reinstall many times, also using control panel, without success...Visual Studio 2017, instead, work correctly: there is the "driver" menu and there is "driver windows kit" between the extensions and updates.I have:Windows 10 Pro, Version 1809.I downloaded the appropriates WDK and SDK version from microsoft site.
As seen in the screenshot, I can't expand my Basic Disk2 for Data2 Volume (F:). This is Server 2012R2 Virtual Machine, Unallocated space of 1TB was added to the VM Disk2 from vCenter Datastore. I tried to reboot the server but getting the same grayed out. Should I try a diskpart option with cmd? Any suggestions please?
So, in order to extend Drive F and make use of that unallocated 1 TB, you'll need to convert Disk 2 from MBR to GPT (GUID Partition Table). The built-in tools won't do this without data loss, so if you want to use the Disk Management console or DiskPart.exe, you'll need to back up your data to another location and then restore it after the conversion.
Windows 10 version 1703 introduced MBR2GPT.exe, which can convert from MBR to GPT without modifying or deleting data. But that's unlikely to be compatible with Windows Server 2012 R2, so it won't help in your current situation.
Yesterday, Microsoft released the first stable version of Microsoft Edge Chromium to the public. Surprisingly, Microsoft Edge is still supporting a number of aging Windows versions, including Windows 7, which has recently reached its end of support.
Earlier, the Redmond software giant decided to follow Chrome's support schedule for Windows 7. As you may remember, Google promised to support the retired OS for at least 18 months, until July 15th 2021.
Today, the company has updated a support document for Edge Chromium, that reveals that Windows 7 is not the only retired OS which is supported by the newest browser. The list is also includes Windows 10 RS3, which is version 1709.
It is mentioned that Windows 7 and Windows Server 2008 R2 will be supported by Microsoft Edge even after those operating systems go out of support. However, IE mode on these operating systems will require the Extended Security Updates for Windows 7.
As for Windows 10 version 1703, Microsoft Edge on this OS should be considered a temporary bridge to getting to a supported OS state. Microsoft recommends upgrading to a newer Windows version that receives updates.
For pre-release versions, Microsoft is currently using three channels to deliver updates to Edge Insiders. The Canary channel receives updates daily (except Saturday and Sunday), the Dev channel is getting updates weekly, and the Beta channel is updated every 6 weeks. Microsoft is going to support Edge Chromium on Windows 7, 8.1 and 10, alongside macOS, Linux (coming in the future) and mobile apps on iOS and Android.
Please update all Comment applications to include DATES, not knowing the date of a posting can completely complicate the use of post. DATES should be a basic design requirement. It is very disheartening to see more and more lax in design standards.
Tip: Winaero Twеaker is essential software for every Windows 10, Windows 8 and Windows 7 user. It allows you to customize the appearance and behavior of the operating system in a flexible way.
Try Winaero Twеaker now!