Micron 3400 NVME SSD firmware update error
I'm attempting to update my Micron 3400 NVME SSD's firmware from version P7MU000 to P7MU002 using Micron Storage Executive, but I'm encountering an error: "PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed". I've attached the relevant images (Attachments 411805, 411806, and 411807). I suspect that the issue is related to a certificate date problem. When I adjust my computer's clock year to 2023, the update finds the new firmware, but it still won't install automatically or manually. Instead, I receive an error. Let me know if you need any further information or assistance!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.)Fast Microsoft recommended driver block rules update with automatic scheduled task
Microsoft recommended driver block rules in Windows are automatically updated starting with Windows 11 22H2, twice per year, but the list itself is updated more often. Microsoft provides ways to update them faster and out of the schedule. I've created a PowerShell script that does this automatically and you only need to run the script once, then it will create a scheduled task in Windows that runs every 7 days and renews the recommended drivers block list. # create a scheduled task that runs every 7 days if (-NOT (Get-ScheduledTask -TaskName "MSFT Driver Block list update" -ErrorAction SilentlyContinue)) { $action = New-ScheduledTaskAction -Execute 'Powershell.exe' ` -Argument '-NoProfile -WindowStyle Hidden -command "& {Invoke-WebRequest -Uri "https://aka.ms/VulnerableDriverBlockList" -OutFile VulnerableDriverBlockList.zip;Expand-Archive .\VulnerableDriverBlockList.zip -DestinationPath "VulnerableDriverBlockList" -Force;Rename-Item .\VulnerableDriverBlockList\SiPolicy_Enforced.p7b -NewName "SiPolicy.p7b" -Force;Copy-Item .\VulnerableDriverBlockList\SiPolicy.p7b -Destination "C:\Windows\System32\CodeIntegrity";$job = Start-Job -Name "Job1" -ScriptBlock { CiTool.exe -r };Start-Sleep -s 15;Stop-Job $job;Remove-Item .\VulnerableDriverBlockList -Recurse -Force;Remove-Item .\VulnerableDriverBlockList.zip -Force;}"' $TaskPrincipal = New-ScheduledTaskPrincipal -LogonType S4U -UserId $env:USERNAME -RunLevel Highest # trigger $Time = New-ScheduledTaskTrigger ` -Once -At (Get-Date).AddHours(3) ` -RepetitionInterval (New-TimeSpan -Days 7) ` # register the task Register-ScheduledTask -Action $action -Trigger $Time -Principal $TaskPrincipal -TaskPath "MSFT Driver Block list update" -TaskName "MSFT Driver Block list update" -Description "Microsoft Recommended Driver Block List update" # define advanced settings for the task $TaskSettings = New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries -Compatibility Win8 -StartWhenAvailable -ExecutionTimeLimit (New-TimeSpan -Minutes 3) # add advanced settings we defined to the task Set-ScheduledTask -TaskPath "MSFT Driver Block list update" -TaskName "MSFT Driver Block list update" -Settings $TaskSettings } https://github.com/HotCakeX/Harden-Windows-Security/wiki/Fast-and-Automatic-Microsoft-Recommended-Driver-Block-Rules-updates
Pilotes error mise à jour de fonctionnalité - Drivers fall in error since last upgrade functionality
Bonjour, (english version just down) Moi et 2 autres amis avons rencontré des bugs malencontreux depuis la mise à jour du 24 mai 2022 : Un certains nombres de pilotes sautent dont les pilotes USB, plus d'utilisation des ports USB... J'utilise une HP z240 et mes amis, l'un un dell et l'autre un lenovo. Après divers tests, nous nous sommes rendu compte qu'en désinstallant la mise à jour de fonctionnalité, cela fonctionne à nouveau. La version incriminée est la 2004. La machine est à présent en 1903. Pouvez-vous m'aider ou m'indique la marche à suivre pour résoudre ce problème ou pour poster un ticket auprès de votre support technique ? Cordialement, Adrien ------------------------English version--------------------- Hello, me and 2 friends had the same big bugs on our computers : Since last functionnality Upgrade some of our drivers fall in error : code 19 Windows can't start this peripheral because the registry informations are incomplete or damaged. the big problem is that USB one is one of them. I can managed to control the machine by RDP. The version of Windows that cause the bug is 2004 : uninstalling the functionality upgrade resolved it temporarily. How to resolve it ? Thx for your help.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.Updated printer driver on server does not update properly on all clients
Hey community We just did an update of the print driver on all our print servers. Most clients downloaded and installed the driver just fine. Some clients had a problem though. The printer queues were still mapped, users were able to print, but the properties dialog was not the one of the driver but most likely the standard MS dialog. After removing all queues and deleting the driver package locally, the printers connected again and downloaded the driver without issues. Any idea on where to look here?There are many similar items in Optional Updates section and I don't know which one to install
in Device manager there are a 4 hardware that need drivers and in Windows update => Optional updates section, there are 7 drivers listed but I don't know which one I am supposed to install. there needs to be more information there to tell us exactly which one to install. there are even drivers listed there with the date 1970! Feedback link: https://aka.ms/AAarmx9Intel 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
