Bluetooth earphones doesn't work in Windows 11
Some Bluetooth earphones (like Haylou GT1) don't work on Windows 11 and it was working perfectly on Windows 10. I think the problem with the drivers and especially with the earphone driver not with the Bluetooth driver because the Bluetooth works normally with the controllers. Just to let you know when I disable the "Haylou-GT1 Avrcp Transport" driver and keep the "Haylou-GT1" driver enable it sometimes works but with very bad quality sound so I am some kind of sure it's a driver problem and that driver provider is Microsoft so I think you can fix it. There is a lot of people who had the same problem, look at this link: https://techcommunity.microsoft.com/t5/report-an-issue/bluetooth-earphones-doesnt-work-in-windows-11/m-p/2554552 I contacted Microsoft support and they say: "Only our engineers have the access to its Windows 11" So they advised me to post in here in windows insider (I don't know why, I am not a Windows insider member, I just downloaded windows 11 when it's released for everyone.)
Can't install our app - "certificate in chain-of-trust is failing validation"
We've had a number of support incidents from users with Windows 11 Insider Preview reporting that they can't install our Windows Desktop app. Users with the retail release of Windows 11 (or Windows 10) do not experience this issue. Our (WiX) installer runs successfully until it gets to the driver installation step. Then it rewinds and quietly exits with no message popup or obvious error. Despite testing with a variety of different Insider Preview builds, we've so far been unable to reproduce the problem locally. Looking at a verbose setup log contributed by a user, I noticed the following: DIFXAPP: INFO: ENTER: DriverPackageInstallW DIFXAPP: INFO: RETURN: DriverPackageInstallW (0xE0000247) DIFXAPP: ERROR: encountered while installing driver package 'C:\Program Files\AcmeWidgets\WidgetApp\widget-driver.inf' DIFXAPP: ERROR: InstallDriverPackages failed with error 0xE0000247 DIFXAPP: RETURN: InstallDriverPackages() 3758096967 (0xE0000247) CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 21:00:47: InstallFinalize. Return value 3. MSI (s) (50:CC) [...]: Note: 1: 2265 2: 3: -2147287035 Our driver is signed with a Digicert EV Code Signing Certificate: Certificate Certificate Order Common name Product Status Order date start date expiration expiration ------------- --------------- ------ ----------- ----------- ----------- ----------- Immersed Inc. EV Code Signing Issued 27 May 2020 28 May 2020 02 Jun 2022 02 Jun 2022 2 years While investigating, I also saw a message/description that mentioned a certificate in the chain-of-trust failing validation. I thought perhaps an intermediate CA cert might have been omitted from one of the Insider Preview builds, so I requested dumps of root, intermediate and third-party certs from a few affected users. My hope was to find a cert included in my test environment that was missing in all of theirs. No such luck, unfortunately; they all seem to have supersets of the certs I have in a fresh Insider Preview test installation. Can someone please respond with a suggestion on a path forward? Being unable to reproduce this in a test environment has me completely blocked. I'd really like to hear back from a Microsoft engineer on this. Thanks.
Can't sign my driver with sha384 EV code signing certificate
Hello, our company renew EV code signing certificate, and now it has sha384 algorithm, our driver correct pass all HLK tests, and after it i have signed my *.hlkx result with this certificate, but micorosoft partener center can't accept this *.hlkx due to error: "Microsoft allows SHA2 only signature algorithm. Please re-sign with a valid certificate and submit again" Help me, please.What makes a driver 'High Impact' vs. 'Very High Impact'?
As a quick reminder, drivers are potential causal factors that affect outcome measures such as, but not limited to, overall employee engagement, a sense of belonging as well as perceptions of a great workplace culture. In determining how we differentiate between Low, Medium, High and Very High driver impact, we use the driver's Pearson r correlation tied to the intended outcome measure. Drivers are plotted on the X-Axis and those with less than a .20 Pearson r are considered “Low” impact drivers. Between .20 and less than .40 are “Medium” impact, between .40 and less than .60 are “High”, and .60 and greater are “Very High”. See the table below for additional detail. Minimum Correlation Maximum Correlation Low 0 < 0.2 Medium 0.2 < 0.4 High 0.4 < 0.6 Very High 0.6 1.0 As People Science consultants, we're always leveraging the Driver Impact report to help us understand how different survey measures impact key outcomes across different populations and tying that back to action taking strategies. We'd love to hear from our community...In what ways have you utilized Viva Glint's Driver Impact report to support key findings in your surveys?Intel graphics driver in Windows Update for IGPU I7 7700K is OUTDATED
On Windows 10 build 20H1 Stable And also on build 19042.330 (slow/beta) ring, the graphic driver that is automatically installed from Windows Update is extremely Outdated. the latest version is 27.20.100.8280 which is officially available on Intel website. but the version that gets installed automatically from Windows Update is 26.xxxxx Feedback Hub: https://aka.ms/AA8r3yx
