xMorpheousx416 Posted August 16 Share Posted August 16 From the news section, @leonsk29 , this is what I was referring to. I don't know how much more of an AMD system I could be using sans a Radeon GPU. I get this on my MSI board and my daughter's ASUS... both X570. Only solution is to use the higher Admin, not that it bothers me.. runs like a champ on that profile. leonsk29 and hellowalkman 2 Share Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/ Share on other sites More sharing options...
+thexfile Subscriber² Posted August 16 Subscriber² Share Posted August 16 I had the same error with my AMD system when I was updating Chipset Driver. ROG STRIX B450-F with a Ryzen 9 3900X. Windows 11 canary build. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924483 Share on other sites More sharing options...
hellowalkman Reporter Posted August 16 Reporter Share Posted August 16 On 17/08/2024 at 01:45, xMorpheousx416 said: From the news section, @leonsk29 , this is what I was referring to. adding the article here for context: https://www.neowin.net/news/windows-hidden-admin-account-apparently-boosting-amd-ryzen-90007000-performance/ xMorpheousx416 1 Share Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924488 Share on other sites More sharing options...
leonsk29 Posted August 16 Share Posted August 16 Wow, weird, yeah. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924524 Share on other sites More sharing options...
+Eternal Tempest MVC Posted August 17 MVC Share Posted August 17 Not sure what the bug is, but caught this in the release notes. https://www.amd.com/en/resources/support-articles/release-notes/rn-ryzen-chipset-6-07-22-037-.html Known Issues Some driver names on a non-English OS may appear in English. The uninstall summary may incorrectly display the uninstall status as Failed. Occasionally, Ryzen PPKG may not install/upgrade. <- AMD is aware of something going on https://www.amd.com/en/resources/support-articles/faqs/chipset-install.html Installing AMD Ryzen Chipset Drivers Before installing the AMD Ryzen chipset driver package, it is recommended to save and close any open applications and temporarily disable anti-virus software. This can help eliminate any potential conflicts during the chipset driver installation process. NOTE! To complete the installation of the AMD Ryzen chipset driver package, you will need be logged on as Administrator or have Administrator rights on the PC. xMorpheousx416 1 Share Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924572 Share on other sites More sharing options...
xMorpheousx416 Posted August 17 Author Share Posted August 17 On 17/08/2024 at 01:52, Eternal Tempest said: Before installing the AMD Ryzen chipset driver package, it is recommended to save and close any open applications and temporarily disable anti-virus software. This can help eliminate any potential conflicts during the chipset driver installation process. NOTE! To complete the installation of the AMD Ryzen chipset driver package, you will need be logged on as Administrator or have Administrator rights on the PC. I could check those things... first off, only Windows Defender is active on either machine. Malwarebytes is installed but free version so it's not actively running in the background, with the exception of the browser plugin(s). I'm quite sure though, that Defender would be running on the primary Admin acct. Per that Note!: yes... that's exactly what we're talking about here... it's not running on the standard admin level acct (first acct created when using your email during OOBE). You have to enable the Admin using CMD prompt, use that profile and it will install. So... if we deduce from basic logic, there's a "right" that's not being given rights to and thus the install fails. There's the question. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924582 Share on other sites More sharing options...
spaceelf Posted August 17 Share Posted August 17 (edited) It's been a problem since I installed 24H2. I don't think they consider it a problem unless it's still happening when 24H2 is released. - https://community.amd.com/t5/drivers-software/chipset-driver-installation-bug/td-p/685291 I could not get the supposed "fix" to accomplish anything either. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924667 Share on other sites More sharing options...
xMorpheousx416 Posted August 18 Author Share Posted August 18 (edited) On 17/08/2024 at 16:50, spaceelf said: It's been a problem since I installed 24H2. It's been a problem for me since AM2/AM3 builds... every board, every CPU/chipset, every time. The screenshot on that page you linked to, I don't get that.. just the error screen. If I get that installer screen things run smooth as jelly, but only on the primary admin acct, not a local admin. And... the first profile I create for Windows during a new install has never had spaces in them either, nor special characters (which used to drive Windows XP crazy with certain installers). Still think it's a permissions issue and AMD is just too lazy to fix it because they think it's trivial. Having to run command options isn't trivial to those that just want it to work. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924804 Share on other sites More sharing options...
spaceelf Posted August 19 Share Posted August 19 (edited) It seems possible the only reason it happened was I'd disabled VBscript? I guess they're still using it even though it's deprecated. Installing fine now. I can't really say I want to keep that enabled though so that might continue being a thing. +thexfile 1 Share Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924810 Share on other sites More sharing options...
+thexfile Subscriber² Posted August 19 Subscriber² Share Posted August 19 I enabled the VBscript and it worked. wow 🤪 Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924818 Share on other sites More sharing options...
bikeman25 Posted August 19 Share Posted August 19 I'm lucky when i updated my AMD chipset drivers on my new Ryzen 7700X build it went fine! Hopefully when i do my clean install soon that goes fine as well Though with AMD being that i'm still new to the platform- do i install the Chipset Drivers, and AMD Aderlin before Windows update or after? Previously with my old Intel builds, i installed WIndows, then did Windows updates, then drivers, but i can do Chipset first, then Video, then Windows update if that is proper way for an AMD System Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924824 Share on other sites More sharing options...
+thexfile Subscriber² Posted August 19 Subscriber² Share Posted August 19 On 18/08/2024 at 22:45, bikeman25 said: do i install the Chipset Drivers, and AMD Aderlin before Windows update or after? I would do it after the Windows update. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924825 Share on other sites More sharing options...
bikeman25 Posted August 19 Share Posted August 19 Ok noted, and will do the drivers after Windows Update Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924826 Share on other sites More sharing options...
Taliseian Posted August 19 Share Posted August 19 (edited) I can second that motion. When I do clean installs I have a method that I follow and part of that is Windows Updates first. The best defense against security issues is an up to date operating system first, then install drivers and apps after. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924888 Share on other sites More sharing options...
xMorpheousx416 Posted August 19 Author Share Posted August 19 Not too far from what others do... Windows, Windows updates, chipset driver, video driver, audio driver, apps. Funny how you all enable VBScript and it works... curious as to why it would be disabled by default on a user admin, but enable by default on primary admin. Even more curious. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598924975 Share on other sites More sharing options...
+Eternal Tempest MVC Posted August 20 MVC Share Posted August 20 VBScript is going to be deprecated, but won't be turned off in windows by default until 2027. Source - https://en.wikipedia.org/wiki/VBScript https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301 Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925019 Share on other sites More sharing options...
sinetheo Posted August 20 Share Posted August 20 DDU. Give that a chance? With Windows I always do a re-image once a year since the days of WIndows 98 this was normal to keep things smooth. If you change any hardware you must always wipe the OS each time as Windows keeps older stuff. My guess is that image was from a different set of hardware so the registry has keys identifying your hardware as something different than now. Backup and do a fresh wipe Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925024 Share on other sites More sharing options...
xMorpheousx416 Posted August 20 Author Share Posted August 20 On 20/08/2024 at 00:37, sinetheo said: DDU. Give that a chance? With Windows I always do a re-image once a year since the days of WIndows 98 this was normal to keep things smooth. If you change any hardware you must always wipe the OS each time as Windows keeps older stuff. My guess is that image was from a different set of hardware so the registry has keys identifying your hardware as something different than now. Backup and do a fresh wipe I'd never use DDU for a chipset driver. I do, however, use it for video. Any hardware? I think not. If you're going from one type of chipset to another, I would agree.. but adding a new sound card doesn't apply here. Or a new network card... some additional RAM, you get where this is going. I've done several new installs on the same machine with no changes to the hardware profile. Last one was with Beta version .4000, just two iterations away from what it is now. Still the same error when using the standard admin acct. It's not a solitary Windows issue or the primary Admin acct would/could also generate the same problem. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925047 Share on other sites More sharing options...
spaceelf Posted August 20 Share Posted August 20 On 19/08/2024 at 23:43, Eternal Tempest said: VBScript is going to be deprecated, but won't be turned off in windows by default until 2027. Source - https://en.wikipedia.org/wiki/VBScript https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301 It already is, unless you think October 2023 is the future. xMorpheousx416 1 Share Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925059 Share on other sites More sharing options...
adrynalyne Posted August 20 Share Posted August 20 (edited) On 19/08/2024 at 14:46, xMorpheousx416 said: Not too far from what others do... Windows, Windows updates, chipset driver, video driver, audio driver, apps. Funny how you all enable VBScript and it works... curious as to why it would be disabled by default on a user admin, but enable by default on primary admin. Even more curious. Its not yet disabled by default for the user, this is something the user would have done. https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301 "Deprecation phase 1 VBScript is available as features on demand (FODs), enabled by default in Windows 11, version 24H2." It won't be a FOD disabled by default until ~2027. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925086 Share on other sites More sharing options...
erpster3 Posted August 20 Share Posted August 20 On 20/08/2024 at 04:42, spaceelf said: It already is, unless you think October 2023 is the future. but October 2023 is actually the past since it's already 2024 Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925106 Share on other sites More sharing options...
erpster3 Posted August 20 Share Posted August 20 On 20/08/2024 at 07:16, adrynalyne said: Its not yet disabled by default for the user, this is something the user would have done. https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301 "Deprecation phase 1 VBScript is available as features on demand (FODs), enabled by default in Windows 11, version 24H2." It won't be a FOD disabled by default until ~2027. that MS link seems to only mention Windows 11. nothing is said about Windows 10 there Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925108 Share on other sites More sharing options...
adrynalyne Posted August 20 Share Posted August 20 (edited) On 20/08/2024 at 08:59, erpster3 said: that MS link seems to only mention Windows 11. nothing is said about Windows 10 there I doubt the timeline is any different past they just might not bother disabling it since most SKUs will be out of support. The important thing I was pointing out is that its currently enabled by default for every supported Windows OS. Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925127 Share on other sites More sharing options...
xMorpheousx416 Posted August 20 Author Share Posted August 20 (edited) On 20/08/2024 at 09:16, adrynalyne said: Its not yet disabled by default for the user, this is something the user would have done. Don't look my way,... any time I enable or disable something I could easily get kicked from the Beta, so I don't go messing with too many settings or options unless it's a change needing a test or two. In Setttings, I don't even have the option to add or remove it. Edit: Just checked my HTPC running the public release of .4035, and it doesn't have VBScript either. Not in Settings' Windows Features and not Control Panel's Windows Features. The board running the HTPC is an AM3+ / FX8350 and she too needs the primary admin acct in order to update the chipset drivers, although it's now been deprecated and is no longer supported with anything new. Alas... it's an irritating bug with an easy workaround, so no worries. Edited August 20 by xMorpheousx416 Link to comment https://www.neowin.net/forum/topic/1445091-amds-chipset-install-issue/#findComment-598925227 Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now