Does Dell even know? The people I speak to on the phone don't know anything. I am supposed to send in my computer (R9) even though it works with the old BIOS without any problems. Is Dell really working on a solution? Dell we want information.
Warranty =/= getting your stuff fixed, from what I hear due to chip shortage they are more focused on new machines than fixing existing machines. If you can get them to admit it was their fault and still have warranty I would push for a new system IMO. There are folks on here that have been waiting weeks for a mobo due to the update bricking their system. I don't know why they would push out a bios update to windows.
My GPU has suddenly started dying, screens go black and the fan revs to max. I swear at this point Dell is trying to kill my PC now that I'm out of warranty.
I was on .16 when my issue began that everyone is experiencing (Was on Windows 10 at the time). It was right after the Alienware Command Center Suite got updated. After that I went back down to .9 then eventually did the bios flash to .17 myself. It broke things again but I was able to turn the PC on by pressing power button multiple times so I was okay with that until the fix came.
I saw last week in Windows Updates Alienware - SoftwareComponent - 1.1.47.0 update. I do Alienware software updates through Alienware's update app so as usual ignored this. Yesterday, for some reason this update installed itself even though it shouldn't have but it fixed the issue. I can now power on as usual and Command Center is fixed as well. It now shows the correct readings for CPU/GPU/Memory instead of 777. I checked daily for the Alienware Update app for updates but nothing appeared except for this update in Windows Update.
No OS updates or software updates were made yesterday on my machine except for this Alienware - SoftwareComponent - 1.1.47.0 update. If you have this Windows Update, I would give it a go.
I am nervous about updating anything now. I never use the Alienware app or OCC , but the last time Alienware updated something for me it did flash the BIOS to a higher one than .09.
I am running everything fine at the moment but it's a case of when not if some update happens or I install some new programme and the nightmare will begin again.
I'm having the same issue with my Aurora R8 after the BIOS update. Still under extended warranty, and I have been on phone with Tech Support, had a service technician come out and replace the pc top with the power button on it, all to no avail. They've now ordered a power cable and a motherboard (which is on backorder until FEB 2022) and asked me to surrender my computer for exchange with a refurbished one. NO WAY!!! These guys are chasing hardware issues with no mention of BIOS, etc. I'm not confident Dell is recognizing this issue and working on a fix to the BIOS and the Windows Update that subsequently causes the power button to seize up. But THANK YOU to all the folks out there for this sage advice how to get it turned back on and to keep this pc running until they come up with a real solution. You guys/gals rock!!
I'm not confident Dell is recognizing this issue and working on a fix to the BIOS and the Windows Update that subsequently causes the power button to seize up.
I suggest you interact with this person if they are from support via private message. I was in a conversation with them for quite a while. They were supportive but are only able to do so much. I also contacted Dell support via telephone. The more of Dell employees that know of your issue the better it will be for you.
I just received a private message from "Paventhan M" from the "Dell Social Media team". Has anyone here had any interaction with this individual? He seems to want to understand my issue. He has not read this thread or any replies. Given this I'm not sure how he can help.
Ad me to the list on this. Firmware upgrade and boom power button issues. More people need to post and contact it is the only thing they respond to are numbers.
Ran into a few issues (related to many posts about the R8) with my R8 that I ended up resolving related to the R8's poor designed case with newer tech.
Anyway, I ran into this issue as well. I felt this issue was intentional by Dell because I almost broke my R8 getting it to power on. It was even worse when rolling back the BIOS, no response after applying to older BIOS. I mean the monitor was black, keyboard and mouse had no power, nothing for over an hour. I took a chance asnd powered off my R8 via PSU reset button, and that worked.
I noticed a few replies where some R8 owners purchased dell support (because everyone should be expired by now) to try to resolve this issue. This is a crime, and those should be refunded. Dell needs to get there act together and support all R8 owners who are having this issue for free. If any R8s bricked and/or broken should be replaced for free.
I test software for a living, and somehting like this should of been caught prior to release.
Misio, how long have you been on Windows 11 and how long was it before the software component update appeared in Windows update? I've done a search for 1.1.47.0 and see no reference to it which I find odd. I'm beginning to wonder if the overclocking control push and this mysterious software push by Microsoft were really intended for a Windows 11 user and sent out incorrectly to Windows 10 users
Can you confirm the component update number as 1.1.47.0? Maybe the only to fix this is go from Windows 10 to 11 and wait for this new Alienware software component to appear.
I think your story pretty much confirms for me that this has nothing to do with the pushed BIOS update per se.
KaiBGM
6 Posts
0
November 15th, 2021 09:00
Does Dell even know? The people I speak to on the phone don't know anything. I am supposed to send in my computer (R9) even though it works with the old BIOS without any problems. Is Dell really working on a solution? Dell we want information.
Haroldwong
16 Posts
0
November 15th, 2021 11:00
Warranty =/= getting your stuff fixed, from what I hear due to chip shortage they are more focused on new machines than fixing existing machines. If you can get them to admit it was their fault and still have warranty I would push for a new system IMO. There are folks on here that have been waiting weeks for a mobo due to the update bricking their system. I don't know why they would push out a bios update to windows.
NevrAgn
2 Posts
0
November 15th, 2021 15:00
My GPU has suddenly started dying, screens go black and the fan revs to max. I swear at this point Dell is trying to kill my PC now that I'm out of warranty.
Misio7
9 Posts
0
November 15th, 2021 19:00
I thought about this but decided against it. Any positive results with it removed?
PalAl
1 Rookie
•
41 Posts
0
November 15th, 2021 20:00
None that I have noticed but I didn’t change anything else to test.
Misio7
9 Posts
1
November 16th, 2021 11:00
My computer works fine now.
I am on the .17 bios and Windows 11.
I was on .16 when my issue began that everyone is experiencing (Was on Windows 10 at the time). It was right after the Alienware Command Center Suite got updated. After that I went back down to .9 then eventually did the bios flash to .17 myself. It broke things again but I was able to turn the PC on by pressing power button multiple times so I was okay with that until the fix came.
I saw last week in Windows Updates Alienware - SoftwareComponent - 1.1.47.0 update. I do Alienware software updates through Alienware's update app so as usual ignored this. Yesterday, for some reason this update installed itself even though it shouldn't have but it fixed the issue. I can now power on as usual and Command Center is fixed as well. It now shows the correct readings for CPU/GPU/Memory instead of 777. I checked daily for the Alienware Update app for updates but nothing appeared except for this update in Windows Update.
No OS updates or software updates were made yesterday on my machine except for this Alienware - SoftwareComponent - 1.1.47.0 update. If you have this Windows Update, I would give it a go.
AnthonyRebel
2 Intern
•
21 Posts
0
November 16th, 2021 12:00
I am nervous about updating anything now. I never use the Alienware app or OCC , but the last time Alienware updated something for me it did flash the BIOS to a higher one than .09.
I am running everything fine at the moment but it's a case of when not if some update happens or I install some new programme and the nightmare will begin again.
AdventureDeb
5 Posts
1
November 16th, 2021 15:00
I'm having the same issue with my Aurora R8 after the BIOS update. Still under extended warranty, and I have been on phone with Tech Support, had a service technician come out and replace the pc top with the power button on it, all to no avail. They've now ordered a power cable and a motherboard (which is on backorder until FEB 2022) and asked me to surrender my computer for exchange with a refurbished one. NO WAY!!! These guys are chasing hardware issues with no mention of BIOS, etc. I'm not confident Dell is recognizing this issue and working on a fix to the BIOS and the Windows Update that subsequently causes the power button to seize up. But THANK YOU to all the folks out there for this sage advice how to get it turned back on and to keep this pc running until they come up with a real solution. You guys/gals rock!!
RobertWJackson
8 Posts
0
November 17th, 2021 05:00
I agree. Still no word from DELL. I have no confidence that a fix is in the works until Dell releases a status report on what they are doing.
KaiBGM
6 Posts
0
November 17th, 2021 05:00
That is my impression too.
PalAl
1 Rookie
•
41 Posts
0
November 17th, 2021 12:00
I suggest you interact with this person if they are from support via private message. I was in a conversation with them for quite a while. They were supportive but are only able to do so much. I also contacted Dell support via telephone. The more of Dell employees that know of your issue the better it will be for you.
RobertWJackson
8 Posts
1
November 17th, 2021 12:00
I just received a private message from "Paventhan M" from the "Dell Social Media team". Has anyone here had any interaction with this individual? He seems to want to understand my issue. He has not read this thread or any replies. Given this I'm not sure how he can help.
Michael2040
1 Message
2
November 18th, 2021 04:00
Ad me to the list on this. Firmware upgrade and boom power button issues. More people need to post and contact it is the only thing they respond to are numbers.
JasonW.
1 Rookie
•
1 Message
4
November 18th, 2021 06:00
Ran into a few issues (related to many posts about the R8) with my R8 that I ended up resolving related to the R8's poor designed case with newer tech.
Anyway, I ran into this issue as well. I felt this issue was intentional by Dell because I almost broke my R8 getting it to power on. It was even worse when rolling back the BIOS, no response after applying to older BIOS. I mean the monitor was black, keyboard and mouse had no power, nothing for over an hour. I took a chance asnd powered off my R8 via PSU reset button, and that worked.
I noticed a few replies where some R8 owners purchased dell support (because everyone should be expired by now) to try to resolve this issue. This is a crime, and those should be refunded. Dell needs to get there act together and support all R8 owners who are having this issue for free. If any R8s bricked and/or broken should be replaced for free.
I test software for a living, and somehting like this should of been caught prior to release.
Jusr fix you issue Dell!
reddrocket
5 Posts
0
November 18th, 2021 08:00
Misio, how long have you been on Windows 11 and how long was it before the software component update appeared in Windows update? I've done a search for 1.1.47.0 and see no reference to it which I find odd. I'm beginning to wonder if the overclocking control push and this mysterious software push by Microsoft were really intended for a Windows 11 user and sent out incorrectly to Windows 10 users
Can you confirm the component update number as 1.1.47.0? Maybe the only to fix this is go from Windows 10 to 11 and wait for this new Alienware software component to appear.
I think your story pretty much confirms for me that this has nothing to do with the pushed BIOS update per se.