(I move to 3.6 only if I have to - 3.5works - so it stays put for me for now)
I spoke to a person just yesterday over CmndCntr & W10; I informed this person that since Dell has turned their backs on fixing the blight that is Aurora on Windows 10 with 100% fans which began nearly one year ago, it is essential that a person take caution with their 10 install & making any changes to it.
Stay with me here Chuck.
I do not understand why you didn't simply boot into your existing 10 install which should have had CC on it already, whatever version you were on pre-MIO swap. If you made a back-up of your 10 install, fall back to it?
Aurora has 4 hard drive caddy's & room for a 5th drive in the DVD bay. May I suggest you - or anyone reading this - invest in several drives, look into free Macrium Reflect Cloning software also.
A scenario for you or others after reading this may be this: clone (or back-up) your working 10 install, twice if need be, the more the merrier; make your software changes to your clone ... if they work, induce the change to your everyday drive - & fall back on your 3rd clone if need be since it will have had no changes imparted to it.
Back to talking shop, I wonder what became of your pre-MIO-swap CC? Explore your options towards getting your 10 drive back to wherever it was a few hours ago before the swap.
Let us pretend you can get back to where you were a few hours ago (back-up / system restore maybe): if no good?, find your CC version in your C:Dell/Drivers folder, launch the actual CmndCntr.exe & click repair. See what happens.
If you can not restore to a prior point, I would make a clone(s) right now (or a back up): you may launch CC3.5 or 3.6 in several ways:
just launch it, see what happens
launch it in Windows 8.1 Compatibility Mode, see what happens
if there is W8 or W7 mode, see what happens
report back
Note however, working on the clone drive as the Sandbox - as Tesla calls it - so u may do as you please, playing in your sandbox clone drive: we do not want the blight of 100% fans now do we Chuck, therefore we must explore several CC versions & many ways to install those versions ... when one does a Goldilox for us? We induce the change on our daily-use drive & what else? Always have a clone / back-up ... think it through carefully how to keep, maintain & restore your 10 install so it will never have 100% fans, that is my best advice.
It's every man for himself up in this joint ...
I have a post with numerous links / tips. If all else fails, read it, find the 5 Command Center links, 2 we know will work, 3 are wild-cards ... all 5 are worthy of trial on a clone drive
Dell will not support your R4 on Windows 10, short of whatever drivers exist on the 10 driver page put there last year on 10's launch day we'll call it: after that they're finished with people like you and I. The only bone they can throw us is to set fan speeds to 'manual' in CmndCntr & turn your back on 'auto' fans as they've done. Follow their lead Chuck: ignore working auto fans for the rest of your life if need be but do not ignore the fact they aren't truly supporting your R4 or mine on Windows 10 with the only issue that truly exists for R4 & truly needs support ...
I will return Monday, but as a last resort?, a hunch tells me this:
disconnect MIO USB from mthrbrd header
power up
launch CC 3.5 or 3.6
if it executes? restart
desktop, power down, reattach MIO USB
power up, surveil for a working environment
If it executed, if, then u have the option now to leave it be - or - sniff in the C:Dell/Drivers folder, launch CC.exe & click repair ... changes like these I do on a clone here Sir, then decide what to do with my daily drive afterwards, do what is right for you & your Alien
note for me please Chuck: Alien-Alex's advice to 're-flash' the Bios? It did not come with the disclaimer that if you brick your motherboard? Which is a common nuisance for the R4 FPV4P & 7JNH0 mthrbrd, that they did not make you flash it - u will have done so of your own volition - & may not be under warranty coverage in the event of a brick. 'Can' re-flash implies a choice ... 'can', if you want to, not because we said to; such language 'can' play a part to undermine a warranty claim as we'll learn.
It is for Alien-Alex to explain why no disclaimer was attached to his advice regarding damage, loss, liability & relief from a bios flash gone wrong. Nor do I see proper safest methods to flash bios in that advice. The last we were told is to be on the phone with a support agent holding your hand during a flash, so if it goes wrong u have a one-time chance at a replacement board; it is for Alex to say if any R4 boards are in stock, ready to ship as a warranty replacement or if none exist in stock.
You will of course inquire of Alien-Alex, won't you Chuck, that if telling you there above to flash your bios - & if it bricks - you can get relief from Dell in the form of a new replacement FPV4P or 7JNH0, based on the words in that post urging u to do so, if the words constitute or imply you have coverage from them, in or out of warranty of course. As an R4 owner, we the people must not go into Bios flashing willy-nilly; extreme care is needed, & flashing your Bios of your own volition by your own two hands may haunt you if it bricks, which these certainly do.
Note that Alien-Alex never inquired what Bios version you are on either Chuck; R4, needs incremental jumps to A11, if you're on a very old version such as A02/03/05 etc ... one doesn't jump straight to A11 for fear of a what? A brick Chuck, a brick.
I see no causal relationship to a failed CC install & your bios version: proceed with caution
we wouldn't want your mthrbrd to brick just so u can have CC working ...
"Discussion = If you are outside the warranty period and loaded the System Bios update without any direction from Dell Technical Support, you must purchase a replacement motherboard and replace it yourself".
We'd like to know if Alien-Alex's words qwalify as 'with direction from Dell Technical Support
"The policy going forward on all Alienware models is that since we do not automatically "push/force" a Bios update on your system, we are not obligated to the replace the motherboard if the Bios update fails".
Simple post on moving from Bios A02 to A11 or the reader can search my profile 'favorites' for Aurora Bios posts, or the forum search box, 'Aurora Bios' as key words.
Tesla 1856 recommends doing the flash through DOS on a flash drive I believe, not executed through windows & a running windows environment ...
Dead R4 board owners - who've bricked their $200 replacement board possibly & probably on their own dime after being given advice by Tech Support that they 'can' flash to A11, with no other advice or disclaimer attached to it what-so-ever, nor asking which Bios version the owner is even on 1st?, & three other mentionables from earlier - may read this thread, chime into this thread, or contact Lord Zog for guidance on a possible repair:
Thanks for the help. I did your steps and then after reboot I could not find CC to uninstall so I don't think it was getting past what ever error it had to get installed.
As for the .NET Framework well I got lost trying to find them to remove. ( Man Windows 98 was easy finding things ) Anyway so I just went and installed 3.5 and it's all good now.
Thanks for the fast reply. I installed 3.5 and it works :) All is good.
I think I may have checked for updates and installed what ever update CC had and that's when all the problems started and I bricked the board. Been awhile now so don't recall for sure.
I know my old board when I would start the pc the lights would flash but the fins would not open so I didn't think the board was bad. So I played around with things for months before deciding to buy another MIO board. I even formatted the partition and put windows back on and tried to get the board to work with no luck. Then went back to windows 10 and monkeyed around some more.
So this is why I didn't have a back up of CC or anything. ( great Idea about the clone drives by the way )
I talked to Dell support when this problem first started but PC was about a month out of warranty and they said it was $300.00 for a new MIO Board so I left it alone for a month after hearing that. After reading in the forum I seen some one said to check Ebay out for a new board from a Texas seller so I did.
Found a match to mine for $30.00 and it showed up today and I installed it and then come here and you know the rest :)
Anyway thanks for the help. 3.5 is working so I will keep it :)
I kind of over looked what he said about the bios flash but some one else reading this thread may try it so glad you posted about it.
My R4 is already at A11 and come from Dell with A11. I know exactly what your talking about though, I have never bricked a MB yet from bios upgrades but I have never done one in windows. Yeah flashing the bios is not for every one and needs to be done with caution for sure.
On another note. It seems like I seen something on how to change the thermal status to F° from C° Not a big deal really just messing around with settings now :)
I am fine with no lights and I love not hearing the fans running so loud. But it would be nice to have CC working again.
Uninstall old version and reboot.
Clean-Install either AW-CC v3.5.x or v3.6.x in Win10/64bit with Windows-8 Compatibility Mode. Reboot.
As always, set to Manual and then an up-hill Curve.
Right click on Thermal-Controller Tray-icon for Settings and set Startup-Mode as auto-start with Windows. If you want Fahrenheit, you can set that too.
Thanks for the reminder. Have it set to auto start and F°
Now my fins on the top of the case are not working. I can hear them trying to open so must be stripped or not set right or something in the case. So will have to check in the case and see if I can fix it.
Cass-Ole
6 Professor
•
1.9K Posts
1
June 10th, 2016 15:00
sure I've seen that before; failed install log; the failure to qwery personality module is normal, the rest?, verbose gobble-dee-gook.
Edit: I see here you've marked this as your answer Chuck & I am thankful that it wasn't verbose gobble-dee-gook to you at least
I'll be on a trip in a few hours, I can't pitch in after this little bit. My R4 is on CmndCntr 3.5 & W10
I spoke to a person just yesterday over CmndCntr & W10; I informed this person that since Dell has turned their backs on fixing the blight that is Aurora on Windows 10 with 100% fans which began nearly one year ago, it is essential that a person take caution with their 10 install & making any changes to it.
Stay with me here Chuck.
I do not understand why you didn't simply boot into your existing 10 install which should have had CC on it already, whatever version you were on pre-MIO swap. If you made a back-up of your 10 install, fall back to it?
Aurora has 4 hard drive caddy's & room for a 5th drive in the DVD bay. May I suggest you - or anyone reading this - invest in several drives, look into free Macrium Reflect Cloning software also.
A scenario for you or others after reading this may be this: clone (or back-up) your working 10 install, twice if need be, the more the merrier; make your software changes to your clone ... if they work, induce the change to your everyday drive - & fall back on your 3rd clone if need be since it will have had no changes imparted to it.
Back to talking shop, I wonder what became of your pre-MIO-swap CC? Explore your options towards getting your 10 drive back to wherever it was a few hours ago before the swap.
Let us pretend you can get back to where you were a few hours ago (back-up / system restore maybe): if no good?, find your CC version in your C:Dell/Drivers folder, launch the actual CmndCntr.exe & click repair. See what happens.
If you can not restore to a prior point, I would make a clone(s) right now (or a back up): you may launch CC3.5 or 3.6 in several ways:
Note however, working on the clone drive as the Sandbox - as Tesla calls it - so u may do as you please, playing in your sandbox clone drive: we do not want the blight of 100% fans now do we Chuck, therefore we must explore several CC versions & many ways to install those versions ... when one does a Goldilox for us? We induce the change on our daily-use drive & what else? Always have a clone / back-up ... think it through carefully how to keep, maintain & restore your 10 install so it will never have 100% fans, that is my best advice.
It's every man for himself up in this joint ...
I have a post with numerous links / tips. If all else fails, read it, find the 5 Command Center links, 2 we know will work, 3 are wild-cards ... all 5 are worthy of trial on a clone drive
Dell will not support your R4 on Windows 10, short of whatever drivers exist on the 10 driver page put there last year on 10's launch day we'll call it: after that they're finished with people like you and I. The only bone they can throw us is to set fan speeds to 'manual' in CmndCntr & turn your back on 'auto' fans as they've done. Follow their lead Chuck: ignore working auto fans for the rest of your life if need be but do not ignore the fact they aren't truly supporting your R4 or mine on Windows 10 with the only issue that truly exists for R4 & truly needs support ...
I will return Monday, but as a last resort?, a hunch tells me this:
If it executed, if, then u have the option now to leave it be - or - sniff in the C:Dell/Drivers folder, launch CC.exe & click repair ... changes like these I do on a clone here Sir, then decide what to do with my daily drive afterwards, do what is right for you & your Alien
Cass-Ole
6 Professor
•
1.9K Posts
1
June 10th, 2016 16:00
note for me please Chuck: Alien-Alex's advice to 're-flash' the Bios? It did not come with the disclaimer that if you brick your motherboard? Which is a common nuisance for the R4 FPV4P & 7JNH0 mthrbrd, that they did not make you flash it - u will have done so of your own volition - & may not be under warranty coverage in the event of a brick. 'Can' re-flash implies a choice ... 'can', if you want to, not because we said to; such language 'can' play a part to undermine a warranty claim as we'll learn.
It is for Alien-Alex to explain why no disclaimer was attached to his advice regarding damage, loss, liability & relief from a bios flash gone wrong. Nor do I see proper safest methods to flash bios in that advice. The last we were told is to be on the phone with a support agent holding your hand during a flash, so if it goes wrong u have a one-time chance at a replacement board; it is for Alex to say if any R4 boards are in stock, ready to ship as a warranty replacement or if none exist in stock.
You will of course inquire of Alien-Alex, won't you Chuck, that if telling you there above to flash your bios - & if it bricks - you can get relief from Dell in the form of a new replacement FPV4P or 7JNH0, based on the words in that post urging u to do so, if the words constitute or imply you have coverage from them, in or out of warranty of course. As an R4 owner, we the people must not go into Bios flashing willy-nilly; extreme care is needed, & flashing your Bios of your own volition by your own two hands may haunt you if it bricks, which these certainly do.
Note that Alien-Alex never inquired what Bios version you are on either Chuck; R4, needs incremental jumps to A11, if you're on a very old version such as A02/03/05 etc ... one doesn't jump straight to A11 for fear of a what? A brick Chuck, a brick.
I see no causal relationship to a failed CC install & your bios version: proceed with caution
we wouldn't want your mthrbrd to brick just so u can have CC working ...
Failed Bios Update, Out of Warranty
BIOS A06 Killed my Aurora R4
Alienware bootup/ restarts after frezzing on installing new bios
"Discussion = If you are outside the warranty period and loaded the System Bios update without any direction from Dell Technical Support, you must purchase a replacement motherboard and replace it yourself".
We'd like to know if Alien-Alex's words qwalify as 'with direction from Dell Technical Support
Alienware Aurora Boot Failure .... 5 beeps
"The policy going forward on all Alienware models is that since we do not automatically "push/force" a Bios update on your system, we are not obligated to the replace the motherboard if the Bios update fails".
Simple post on moving from Bios A02 to A11 or the reader can search my profile 'favorites' for Aurora Bios posts, or the forum search box, 'Aurora Bios' as key words.
Various:
Tesla 1856 recommends doing the flash through DOS on a flash drive I believe, not executed through windows & a running windows environment ...
Dead R4 board owners - who've bricked their $200 replacement board possibly & probably on their own dime after being given advice by Tech Support that they 'can' flash to A11, with no other advice or disclaimer attached to it what-so-ever, nor asking which Bios version the owner is even on 1st?, & three other mentionables from earlier - may read this thread, chime into this thread, or contact Lord Zog for guidance on a possible repair:
cdplatt1965
24 Posts
0
June 10th, 2016 17:00
Alienware-Alex
Thanks for the help. I did your steps and then after reboot I could not find CC to uninstall so I don't think it was getting past what ever error it had to get installed.
As for the .NET Framework well I got lost trying to find them to remove. ( Man Windows 98 was easy finding things ) Anyway so I just went and installed 3.5 and it's all good now.
Thanks for your reply.
cdplatt1965
24 Posts
0
June 10th, 2016 17:00
Cass-Olé
Thanks for the fast reply. I installed 3.5 and it works :) All is good.
I think I may have checked for updates and installed what ever update CC had and that's when all the problems started and I bricked the board. Been awhile now so don't recall for sure.
I know my old board when I would start the pc the lights would flash but the fins would not open so I didn't think the board was bad. So I played around with things for months before deciding to buy another MIO board. I even formatted the partition and put windows back on and tried to get the board to work with no luck. Then went back to windows 10 and monkeyed around some more.
So this is why I didn't have a back up of CC or anything. ( great Idea about the clone drives by the way )
I talked to Dell support when this problem first started but PC was about a month out of warranty and they said it was $300.00 for a new MIO Board so I left it alone for a month after hearing that. After reading in the forum I seen some one said to check Ebay out for a new board from a Texas seller so I did.
Found a match to mine for $30.00 and it showed up today and I installed it and then come here and you know the rest :)
Anyway thanks for the help. 3.5 is working so I will keep it :)
cdplatt1965
24 Posts
0
June 10th, 2016 17:00
Cass-Olé
I kind of over looked what he said about the bios flash but some one else reading this thread may try it so glad you posted about it.
My R4 is already at A11 and come from Dell with A11. I know exactly what your talking about though, I have never bricked a MB yet from bios upgrades but I have never done one in windows. Yeah flashing the bios is not for every one and needs to be done with caution for sure.
On another note. It seems like I seen something on how to change the thermal status to F° from C° Not a big deal really just messing around with settings now :)
Tesla1856
8 Wizard
•
17.4K Posts
3
June 10th, 2016 23:00
Uninstall old version and reboot.
Clean-Install either AW-CC v3.5.x or v3.6.x in Win10/64bit with Windows-8 Compatibility Mode. Reboot.
As always, set to Manual and then an up-hill Curve.
Right click on Thermal-Controller Tray-icon for Settings and set Startup-Mode as auto-start with Windows. If you want Fahrenheit, you can set that too.
cdplatt1965
24 Posts
0
June 12th, 2016 12:00
Tesla1856
Thanks for the reminder. Have it set to auto start and F°
Now my fins on the top of the case are not working. I can hear them trying to open so must be stripped or not set right or something in the case. So will have to check in the case and see if I can fix it.