BIOS update (1.4.4) messed up my laptop

Quick update... After a new visit to this page: http://www.dell.com/support/article...intel-me-txe-advisory-intel-sa-00086-?lang=en I scrolled down to AW17R3 where the bios (1.4.4) and the Intel(R) Management Engine Components Installer was posted. I downloaded the correct version ( 7CDG2_11.7.0.1054) and just run the installer. After a restart I ran the intel tool and was happy to see this:

 

Same MEI driver for 15 r3/17 r4 was supplied for Echo models 15 r2/17 r3. I downloaded them as soon as they posted which got removed after few days and fortunately I was able to rollback to 1.3.12 and still on 1.3.12 with updated MEI FW.

 

The warning is due to new iCLS key being needed after the security breach. Grab Prema's tool and update it to 11.8.50.3448 that fixes strange corruptions when ME is read/queried. The changelog can be found at Win-raid or station-drivers.com

 

I am not wondering if a few of you people aren't having problems because of constant messing around with forward/backward flashing of BIOSes???

I mean a modern-day BIOS image is much more than just a BIOS flash, there is other firmwares, CPU patching, etc that goes on.

Just like people that try to say that you should flash one version to the next of BIOS updates to get current. That just imposes the same problems other have into their system vs a flash from an early rev to the latest in one jump. ie, it is much better to have one set of changes vs set after set after set that has the much higher possibility of corrupting things or applying a faulty patch somewhere along the line (and yes, new BIOS are not only an indicator of a bug being fixed but also a faulty set of patches being fixed as well).

I mean, I understand that misery loves company and people don't want to feel that they are the only ones to get screwed, but screwing up everyone elses setups with faulty advice is in no way a proper solution set. If I had an idea that my system wasn't updating properly and didn't run as is should I sure as heck wouldn't advise anyone else to follow my pitfalls.

And, yes, flashing MEI images that are not authorized and messing around the way you do Vasudev is exactly all the above. Sorry to single you out, as I really think you want to help others, but your entire setup is corrupt, on many levels, I mean all this Prema ignorance cannot even be trusted as the guy could be a higher level hacker that is infecting all the systems that run his low-level updates with viruses/malware. Yet you have his video BIOS (and you cannot say his stuff only modifies the stuff he "says" it does as you have not done a forensic analysis of a system before/after) and now his MEI patches, etc.

Again, great if you want to take the risk, but it is obvious that others have been just as successful (ThomasAAT) using all alienware proscribed and authorized updates and is properly patched.

I mean I understand a lot of people are having issues on a myriad of subjects in regards to BIOS updates, but again, how much of that is by following faulty advice, or by flashing earlier faulty BIOSes in the first place.

I flashed from 1.2.8 to 1.3.12 without issue. I updated various other firmwares (thunderbolt, etc) using the dell supplied updates, again without issue.

I refuse to do 1.4.4 since I personally feel that it is a flawed update based on a hacked cpu microcode "fix" that is being used by Intel to "test the waters". Based on Dell/Alienware and a number of other vendors being reluctant to release BIOS updates that are "known good" that I feel the vendors themselves are also waiting for "proper" fixes. It would seem as if the Skylake platform was chosen as a "not too old, yet not latest gen" platform to "beta-test" the fix on to see how people react to the "hack-fix" they have done.

Once exploits and real threats start emerging is the time that the vendors/Intel will be pressured to provide real security fixes that are done properly. As it is I am hoping they are taking this time for further development/engineering to provide fixes that have the least amount of impact and provide for a proper operating system. Hell, for all we know Microsoft will end up being the "real fix" on the software side (and yes, I am ignoring linux and all the varients because I personally do not care, these systems are sold primarily as Windows 10 machines and that is all I am referring to at the moment).

And, as a side note, it is already known that the 1.4.4 BIOS update breaks the Alienware Graphics Amplifier link on some/all systems and since I have a AGA I will wait until I hear that part of it is fixed in a future BIOS as well.

 

Constant BIOS updates are not a problem unless you love buying BGAs when Flashing fails.
Flashing in simple terms is like re-flashing your Phone's System OS regardless of platforms.
The problem with BIOS flashing if you follow write/erase P B and N blocks before an update to get a clean slate every time after an upgrade will make your PC/lappie to work as intended.
I never forced this update on anybody and asked them if they feel insecure and impatient getting update from Dell, then consider my guide. Then again I am saying this isn't a force-feeding some kind of Cynano compounds to your mouth.
You can station-drivers and verify the hashes since all vendors use the same BIN file to flash MEI and no secret sauce to stop throttling and other ****e.
I did put a cautionary word of advice for people who aren't confident about Flashing anything when risk involved is same as Stock Dell/any vendors BIOS flashing.
If you're too security conscious, stop using the PC altogether and even don't use Prema's tools. So, post your rants elsewhere where somebody cares!

 

Vasudev, and there you have it... You basically have shown that you don't have a clue and are a full-on Prema fan-boy... All the "Prema" tools are written by someone and you are expecting others to trust that it is not malware when they run it... Based on your actions I would more than likely believe it *IS* malware and at that, that you know it.

If you hate BGA systems so much, by all means please move to another computer altogether and stop posting on here. It is obvious that Dell/Alienware is making computers how *THEY* want to produce them and the majority of consumers don't care of they are BGA.

It is obvious that you cannot hold a conversation at a reasonable level and are as immature as you come across...

I do also believe you have shown to be an unreliable and ineffective advocate for anything that will leave peoples systems stable and in a condition where it can be relied upon.

Some of us have been involved with computers for longer than you have been alive. There is much more to be said for BIOS updates than you would like to believe. It is obvious you are a "theoretical" type with no clue how things really work. All systems outside of academics are "exception-based" systems, regardless of the intent on how they are "supposed" to run. What do you think exploits and security flaws are? They are "exceptions" to the design.

Just like BIOS updates are supposed to just "work", yet flashing is still wrought with peril in that there are dozens of "bricked" computers because of invalid flashes, and there are even more "unexpected problems" because flashes will break something because of other flaws in the flashing process. Computers are extremely complex electrical devices, in that "theoretically" all systems should run the same, yet put 5 systems next to one another and outside of heat tolerances you also have all 5 systems running with slightly difference variances. Some run faster, some slower all on the same hardware. That is due to exceptions in the various components on a manufacturing level. Some components will generate more noise thus causing an automatic throttling to keep the noise under control, some will generate noise outside of spec and not be caught and wreak havoc on other systems that are sensitive, etc, etc...

Look at windows system updates. How many thousands of systems end up getting irreversible errors on an update that requires a full OS "reset". In Windows 7 it was extremely rare. In Windows 10 it is much less rare and having to "reset" is actually viewed as a viable solution. That is insane. Personally, I have run into the "reset" situation on two seperate systems after the Windows 10 Fall Creators Update. It also has "broken" sleep mode on older systems. How the heck is "sleep" being broken an acceptable issue that gets no resolve (oh, yeah, that is right, MSoft and Intel don't care about older systems and want everyone to upgrade so they can soak everyone for even more $$$, silly me).

My point is, "exceptions" are becoming the norm and it is a sad situation. Especially on systems that are within a year or two of manufacture. The only way Dell/Alienware/Intel will provide proper "fixes" is to be motivated to do just that. No sort of "hacking" will be a proper fix in a sub-system mix that exists today. It may work for what you want to do, but when someone else goes to do something and finds it broken, then finds because they applied "your fix" they are screwed in applying a proper update, then they are left waiting for someone else to "fix your fix"... See the craziness in that???

 

guys chill.. no one is giving false information, offcourse no one wants to ruin someones dream machine, he wrote those guides with a warning, this flaw was discovered almost 2months back, yet dell cant produce a proper bios update with firmware in time, testing takes time, intel is struggling with their new lineups, ME firmware flashing its been there for quite sometime.. im not going against anyone.. it could be compromised ME firmware which prema uploaded, or it could be the proper one, we cant judge anything.. and please dont talk about the experience here in the forums.. which will only make attitude issues, im already in touch with dell officials locally and alienware reps in forum, since the ETA is longer, those who want it fixed can try prema tools on their own risk.. or wait for dell official bios or ME standalone update.. @Alienware-Wasserman @Alienware-L_Porras @Alienware-K_Castro @Papusan @judal57 @iunlock guys any suggestions ??

 

I agree. No need to start a keyboard war over this. In the end we are all in the same "boat" so to speak and enjoy our computers and want the system to function as intended.

As for my system runs smoothly and the test shows that I am protected and with the updated CPU microcode and now also the ME firmware. I guess I'm all set.
I just wanted to show and provide information on that the recommended process from AW/Dell/intel have worked (for me) from the first day the bios was flashed from 1.3.12 to 1.4.4
As far I understand the official bios for AW17R3 IS 1.4.4 with the provided installer for the Intel(R) Management Engine Components posted by dell: http://www.dell.com/support/article...intel-me-txe-advisory-intel-sa-00086-?lang=en

 

do u mind passing me your Jan Bios 1.4.4 i just want to test it for others.. if it really contains the ME firmware, i will test it and see how it goes.. ill check the SHA256 as well

 

Sure no problem! I have saved all the bios versions from 1.2.8 to 1.4.4
Do you have a email I can send it to?

 

If you have read my many post last years, you should seen that Dell and firmware is a HUGE mess.

You almost said you have been with computers 1, 2 or +3 decades. Then you shold manage to push out some real proof for your claims/allegations.

See bolded text above.

Yet another allegations. Please post proof.

See above.

You still push claims/allegations. How long have you worked with computers? And big known OEM's/resellers who use Prema firmware for their computers, all sell spybox? Big claims!!

I'm sure you manage to see his hardware sig.

And here we go again. And you, you are the only who have the clue on how things really work? Come with some proof for what you push out.

 

Don't waste your time with silly people Brother @Papusan. It's clear this clown doesn't know Brother @Prema and also has no idea what in the world he is talking about. We don't need to care what his opinions are because we know that Prema has amazing talent and is one of the kindest members of our community. I've had the awesome pleasure of working closely with him on multiple projects and to say he is amazing would be an understatement. There is no way he is going to do improper things for personal gain. His firmware mods are far more trustworthy and secure than the broken filth rolled out by the system manufacturers. People that make such ridiculous statements and hurl unfounded accusations are just silly stooges that deserve to be ignored.

 

i have all the bios dump of both alienware 15 R1 and R2.. from 1.1.0 to 1.4.4, except 1.2.3 and 1.4.4 Jan Version.. can you do a Sendspace or wetransfer using 7z or rar format ??

 

I can do that (Sendspace) this evening/as soon I am on my AW.

 

@95TA @Vasudev @Papusan is this enough ?? or need any other proof .. one original firmware from winraid other one is from prematool.. both bins are same.. like i said.. @95TA you need to show some respect to others, even though you could be a pro.. just for the sake of community..

 

Certainly looks like it. Enough for me.

 

Here you go @VICKYGAMEBOY : https://www.sendspace.com/file/bg2wgb

 

Another reason why OEM's can continue to push out garbage. People lack knowledge, think they have the right proper knowledge, not very interested in technology or as you say is just silly (can also be a combination). As you and I know, age does not mean that you have more knowledge than younger people. Push out or state "Some of us have been involved with computers for longer than you have been alive" as a truth that they know better than others falls on his own ignorance.

InSpectre is a tool built by security researcher Steve Gibson.. A very familiar personality in the computer world security. You can of course use a older cpu microcode and deactivate M$ patch to check. But why bother?

And Intel have developed the Intel Sa detection tool. Some as you know (have seen in this thead) don't trust what Intel does. But this seems good.

 

Wow, a lot of OEM hate here... I guess if you all hate your laptops so much, sell them off and go buy a different brand...

Actually, I don't know this Prema fellow at all... He could be genuine and only looking to help, if that is the case, great. But hacked BIOSes and (more directly) tools that allow you to do your own hacking is just asking those that don't have a clue to screw something up. Then you have fan-boys like a bunch on here that push solutions that *MOST* users shouldn't be touching. That is the whole point here. I didn't say the guy doesn't know what he is doing. Just that your all are really piss-poor representatives if you push his hacks as solutions to all problems (and I gurantee they are not, and it doesn't take someone knowing all the intricate details to know that). A hacked video BIOS to speed up things means nothing. A hacked installer to push a new MEI means nothing. Hacked BIOS images to allow for overclocking, again, means nothing. That is the point. What else is there that is a "fix" that makes anyones system more stable, run properly and be more reliable? A hack is not a OEM level "fix" for any of those things. And yes, sometimes the OEMs have a damn good reason for not implementing fixes, and sometimes they are just greedy and want to spend as little money on older system support and just expect the end users to buy newer systems instead of actually engineering fixes (and yes, I am with everyone that in those situations it SUCKS! but we all can vote with our pocketbooks and not buy the newer "fixed" systems to show our displeasure as well).

To clarify, I don't have to prove anything. If it isn't provided by the manufacturer (OEM or Intel or Microsoft) then the majority of users (and most certainly anyone still within warranty) should NEVER use those tools. And in this day and age of malware popping up in everything, you can never be too safe, plus who wants to risk bricking their systems??? Again, most should not be touching those hacks. Yet that is all that is pushed because what you guys really want is a different system altogether. It just doesn't make sense.

I more than understand BIOSes and various other architectures (I actually wrote a bunch of the shared memory architectures, since I have been around since the days of SCO Unix, which was the grandfather of all modern *nix implementations, as well as such large scale systems as doing work on the original Terminal Services architecture back in the late 90s, which is the grandfather of current cloud computing efforts, just to name a few of the things I have been involved in, not to mention having an understanding of and having written compilers, interpreters, actual language sub-systems, low-level drivers of all sorts, coding in dozens and dozens of languages on just as many systems, tons of "real-time" systems and optimizations, etc, etc, etc). Oh, and yes, I am in my mid 40s, so I am not some kid in college, I have done a ton of work in the "real world" where customer support, 100% up-time and reliability all matter.

Personally, I run completely modified BIOSes in a few of my machines (usually after they have been dropped from support by the original manufacturers) to implement new CPU types/microcodes, etc, etc...

My point is that none of this is in any way a *fix* for any of the real problems that millions of end users are facing because of Meltdown/Spectre and other exploits... Basically the attempts here are more noise and peril for most users since there is a host of problems Dell/Alienware needs to fix. If it was one small thing or another, so be it, but these are major issues affecting very expensive high-end machines. We NEED a set of properly engineered and tested fixes for all of it, not some sort of piecemeal attempt at hacking a system (and all while bemoaning all the manufacturers while your at it as happens all the time around here)...

Papusan, you obviously hate your BGA system, right along with Vasudev, so why not both of you sell them off and not let anyone else have to listen to the constant *****ing and moaning. Until recently Alienware wasn't even here and if you think anyone from their camp is going to listen to either one of you, you are insane. Immature rants only make those reps NOT care to be involved here, especially when you both "muddy the waters" with hacking advice that in no way, shape or form fixes peoples problems in a proper manner. You guys are obviously more worried about benchmarks than actually using your systems. The rest of us have lives and don't care for "hacks" and want properly formulated solutions from the vendors.

 

If all should rely on Dell. All you can risk is this!! A Crippled system who never ever will work as intended. And this is pure fact. The 799MHz ThrottleGate live its life today. 3 years after it was released!!


This is your own words...

This ain't a BGA system. It's a Prema powered Clevo system

 

See, that's the trouble. Companies that build laptops DO NOT release properly formulated solutions. They (all of them) release laptops that are broken, crippled, castrated messes. And, that applies to their hardware and firmware. They are mostly incompetent.

 

no offense, i am just a random noob lurker here.. lol.. but from what you are saying all we have to do is follow OEM.. as far as I remember @Mr Fox always rant(rant might be a wrong word to use) on people(fan boi/lack of knowledge) who use Microsoft Windows 10 just for the sake of it colored pastel design but really flawed within.. my point here is you are asking ask to be a sheep to just follow the OEM which is why like tge redmond people abuses this and nothing will change but getting more and more crippled machine or software.. People like Papusan Mr Fox Phoenix Vasudev and etc.. Re people who really trys to help and educate people who lacks knowledge about the computing world so that Big OEM will/might stop abusing power and do there jobs properly.. Which is why if only they have a good competetor.. we users would be a happy bunch.. from reading your post my first impression was like "he works for dell" this is just me assuming.. lol.. anyways I am one of the happy user that prema help with his modded vbios.. hehehe..
edit: sorry for the horrible english.. lol

 

And for other people who want everything stock( ie dont want any kinda mods), these companies dont even sellthe solutions. I mean i heard of create-problem-sell-solution policy, but this, create-problem-and-act-like-its-nothing is kinda annoying.

I really think of this world, these OC people's future if guys like you or @Prema etc werent present! (As far as i belive, clevos wont be "clevo" if prema wasnt there)

 

Fox and papusan always push their system to oblivion to get monster cpu speeds actually usable for 24x7.

 

I think you are mostly correct. Clevo's success with performance enthusiasts is mostly attributable to @Prema. I think the brand would be laughing stock without his firmware mods. I have said this many times, and it is true. I do not want to own any laptop, regardless of specs, if I cannot have @Prema BIOS on it. I have never seen a laptop that did not suck with a stock BIOS. Some suck more than others, but stock BIOS on notebooks is a ludicrous joke, engineered by retards.

And, I am not talking about only the subject of overclocking. If I own something, it's mine. I alone have the right to decide how to use is. That means the decision to enable or disable whatever I want to enable or disable is mine alone to make. We all have the right to access whatever settings are accessible and hiding menus for options like UEFI, CSM, TPM, Secure Boot, memory management, power management, security features and other firmware controls, etc., etc., can only be viewed as an evil control freak's act of violence against consumers.

 

If any of you think that a few hacks on some forums are going to get someone like Alienware/Dell to make their subsystems an open architecture and share with a public-domain hacker like Prema, you really have ZERO clue about how big these companies really are. It will not happen, AT ALL, EVER!

And, if what you guys are saying is true, that you all run Clevos with Prema BIOS and such, what the heck are ANY of you doing in a Dell laptop forum??!?!??

I mean, honestly, if you detest these machines, then you are already an invalid resource for anything.

Seriously, why is Papusan, Mr Fox or anyone else NOT running an Alienware system doing here, *****ing and moaning and berating the products the rest of us have spent money on???

This kind of stupidity doesn't make sense. And don't say it is because you are looking to help people when all you guys do is bash the products and company that produces them on every occasion you post.

It looks like the fan-boys are sticking together like any kind of gang does. No real help, just gloating and berating and trying to get others pissed off like you are.

Again, I too have a distrust of OEMs and big business, but I have valid reasons, not a bunch of excuses that amount to something of the "I am too elite for that broken crap" line you guys are shoveling. And the only way to get the OEMs to fix their problems is by talking to the OEM, not throwing a temper tantrum on a forum. Especially not one where haters that don't even own the systems with problems congregate and bemoan the issues.

 

Oh, and in regards to a locked BIOS "subsystem" where everything is locked down, that is because these systems all include warranties. Those warranties are based on a given systems specifications, and with that the design to properly cool, power and allow for a system to run long-term.

When you want to hack around and change clocks and modify settings and such beyond the original design and specifications, you naturally need to void the warranty that was provided to protect the consumer under the original specifications. How is it right that an end user over-volts, over-speeds and under-cools a system by controlling everything outside of the systems design and then it would be expected the manufacturer would cover any damage under any sort of warranty???

It isn't expected, that is why these systems are locked down. You want an open system, buy a Clevo. you want a well-engineered, designed and reliable laptop for gaming that you don't have to mess with, buy an Alienware. You want a business laptop that has tons of expand-ability and is built for business use, buy a Latitude. You want the same on a consumer level machine, buy an Inspiron. You want a high-end user experience for the consumer, buy an XPS.

There are tons of laptop makers and all design and build their systems within a set of rigid specifications that they are willing to warranty. It is up to them to lock them down and protect themselves. Don't like it, buy something more open.

Now you know why people build their own PCs vs buying pre-built. No different. Dell/Alienware doesn't sell open-design PCs either, so to think their laptops should be more "open" is just foolish.

 

Well, truth be told, @Papusan and I both used to be huge Dell XPS and Alienware fans and I spent a small fortune on the brand back when they were still producing respectable products. There were many others who have also had to deal with their disappointment and moved on to better things. Probably 60-70% of my +30K contributions to this community were in the Alienware threads before they left us high and dry with nothing but worthless BGA filth. And, even then I used to use firmware mods from @svl7 because their stock BIOS and vBIOS were crippled garbage like all the other notebook vendors. Cancer firmware has been a problem for notebook enthusiast since the beginning. It has never been worth a damn, and never will be. But, that's status quo for the industry, not an exclusive Dell/Alienware feature problem.

Then, one sad day, along came the Alienware 17 (Ranger) and Alienware 18 (Viking)--the last two respectable models they sold--with their new breed of crippled filth firmware, carefully crafted to stunt performance and block unsigned firmware mods. That was 2012. Immediately after that is when they went ape dukey on us and ditched socketed CPUs and MXM cards for the soldered trash they sell today. Quite the horrible shift... flipped a switch and went from King of the Hill to Masters of the Dung Heap in a single bound. Things have only gone down hill from there. Extremely unfortunate, but that's the way the cookie crumbles. Clevo and @Prema have been a Godsend. They were ready and waiting to fill the huge void Alienware left in the enthusiast market, and Clevo have only gotten stronger as a brand since Alienware committed Harakiri.

But, since you are new here, it only makes sense that you are not aware of any of this. Perhaps back the in the day when they still made awesome products was before your time and you never had the pleasure of seeing how great they used to be. The Alienware brand used to be something really special and amazing. Before Dell bought Alienware, XPS set the standard that others aspired to in notebook design. The proverbial "good old days" LOL.

And, for the record, we still own an XPS 15. It's my wife's machine. It's nice looking, with lots of aluminum and Gorilla Glass edge-to-edge display, carbon fiber bottom... very attractive and made well, but truly pathetic in terms of performance and configuration options. She's happy with it, so I'm happy for her. It does nothing for me. It's just a nice looking, very well made laptop that has sucky performance like everything else that it competes with.

 

I have still my Alienware. From your own post... Click the added links
"you want a well-engineered, designed and reliable laptop for gaming that you don't have to mess with, buy an Alienware"

"You want a business laptop that has tons of expand-ability and is built for business use, buy a Latitude"

"You want a high-end user experience for the consumer, buy an XPS"

It's a reason people want to thinker with what's wrong with what they have spend money on.

Edit. And there is "not a few" AW owners who have asked me for help in PM. As well people with notebooks from other brands. I can tell you so much... Not a pretty sight that pops up!!

 

After reading this post I installed them on my AW17 R3 with AGA and it is running good with no noticeable difference apart from the USB-C port has a hub attached and when the USB adapter for my Logitech G933 headphones are plugged into it has audio crackle though it but when plugged into a USB on the laptop it doesn't.

Even run a benchmark on tool that I run recently and it got a higher result.

The Intel tool says it is patched and InSpectre tool say NO to both and this is what some powershell check says so not sure on what the deal is with it.

 

Meltdown and Spectre vulnerabilities are not the same flaws as INTEL-SA-00086 (Me flaws).
What Windows Build running? Up to date with patches from Microshaft Update (Intalled the patch who disable the protection?)? Downloaded latest version InSpectre tool?
Run InSpectre tool as adm and see if you can enable Meltdown and Spectre protection. Then reboot and run the tool again. Remember you need the latest bios with the fixes.

 

Windows 10 Home Version 10.0.16299 Build 16299.125 windows update is up to date.
BIOS Version/Date Alienware 1.4.4, 08-Jan-18

Just did the troubleshooter for windows update and this error come up
Potential windows update database error detected.
so trying the fixes for it now

 

http://forum.notebookreview.com/threads/windows-10.762434/page-470#post-10680920

 

Well windows update is broken and have tried a few fixes but it still says up to date.

Just seen the link and out and about right now so when I get home I will try it.

 

All good now thank you for the link.

 

Did you use Prema's ME11 tool or Win-raid link I posted earlier? You have older MEIFW and newer one is 3448. Do note its optional update and nothing serious. If you are like Phoenix then you can update to latest MEFW 3448.

 

And there you go... Vasudev just will NOT stop in recommending updates that are not necessary or authorized...

 

and you came all the way just to post this ?? cmon if you dont want then ignore, why dont u test the firmware byurself or give us a ETA of new firmware from Dell.. are you in touch with Dell Reps.. whats your suggestion

 

I think He is a Dell employee or even Frank Azor himself.

 

Nope, none of the above...

It is just Vasudev somehow wants others to be his beta testers to hacks he is trying, which is wrong in all cases...

Basically he just wants to be validated for his hack attempts... He is too much a Prema fan-boy and wants people to be his fan-boys... Since it is obvious that his MEI installs don't mean much and Dell already has specified a different MEI package and others have reported it works along with the requisite Microsoft patch.

Vasudev is just looking for validation. What is sad is that it is at the cost of others attempting to use hack tools and non-Alienware specified component versions, which is the whole issue here.

 

I saw @a_lunatic running the tools after applying bios and ME firmware. I did the same and mine passed (all green):

 

ThomasAAT, thank you for verifying that Alienware/Microsoft have a valid fix that works.

Do you have a AGA?

If so, any problems running with it after the updates?

There is feed back that 1.4.4 breaks use of the AGA.

 

@ThomasAAT i can confirm that both jan and feb 1.4.4 bios are same, and it doesnt update intel ME firmware to 11.8, ive flashed three times previously with different methods, all same, did u see any me firmwre screen update when flashing BIOS.. or did u use the 17R4 ME standalone updater ??

 

Both are one and the same.
No I didn't new ME flash screen whilst using Dell GSet, it was stuck on Updating ME but canceled out for some reason and said BIOS update successful and I rebooted. Maybe it exited due to LocalMEUpdate being disabled.

 

Vasudev, VICKYGAMEBOY was not referring to you. He asked ThomasAAT the question.

VICKYGAMEBOY, you are illustrating my concern, that in screwing around flashing all these BIOS images, and that in various ways (instead of the straightfoward two ways proscribed by Alienware) that somehow certain flags are getting set/unset and you are not getting a proper flash for the BIOS image provided.

That is the whole point I am making here, that maybe Dell/Alienware is making some grand "assumptions" as to the state of things in peoples machines and too much "mucking around" is leaving things in a state where a "Alienware update" is not doing what it is supposed to because things are not how they are supposed to be.

Now, that is not to say that 1.4.4 isn't flawed, as we all know it does have some issues (as it already been confirmed by at least one Alienware rep), but it would seem that under "ideal conditions" it does flash and do what others expect it to do. Just because it won't flash your system to Intel ME 11.8 doesn't mean that it doesn't include it. That is probably either one of the "flawed" components of this BIOS, or at least your system was in a state where the update could not be applied.

 

so basically flashing from bios to bios can cause issues? If I remembered correctly one dell staff inform me to update bios in order instead of jumping right away to reduce risk of bad update and bricking..

 

Sometimes it can. If Dell doesn't preserve SMBIOS settings and reset to defaults after every update then the issue is most likely to be non-existent.
Think of multiple W10 upgrade causing decrease in performance and odd behaviour from Windows. Similarly, BIOS can have that effect too.

 

The issue with BIOS flashing is the possibility of errors. Without going into great detail, computer memory is different than flash memory (and by flash memory I am talking the kind of memory used for BIOSes, not the flash memory used for SSD storage/SD cards/etc) and even though the process *should* be checked, double-checked and check-summed during writing you still run the risk of single or multiple bit errors.

BIOS flash memory is not meant for heavy-duty write cycles. Why should it be, considering you write to it once in a blue-moon and never have to write to it again. It has, pretty much throughout PC history, been one of the most susceptible processes to "transient errors", be it a power glitch, hardware problem, single bit error (which is somewhat not too uncommon but not noticed with error calculation cycle techniques employed in computers elsewhere in their systems) or just somebody knocking a machine during a write. So until manufacturers spend a little more money (and we are talking cents, not dollars) in changing the technology used for BIOSes (and there most certainly are "iron clad" systems out there that can flash BIOS images all day and never get an error) we are all stuck with the possibility that a hardware/software issue can cause a BIOS flash to cause errors and totally screw up and possibly brick our machines.

And that is without adding in the possibility of someone messing around with malware, viruses and any other number of malicious attempts to compromise systems.

That is also why there are stringent notices about how and when to flash a BIOS image.

Basically the BIOS is how it all gets configured and started up, and there is no checks and balances on how it all works. It is "assumed" that the image flashed is proper and operational when you flash it and how you flash it.

Thus you should only flash if you need to and when you need to as to fix known problems. Flashing BIOSes left and right playing around is a "at your own risk endeavor" and is ALWAYS a risk.

Fortunately, for most, flashing is a very rare occurrence, thus minimizing the possibility of problems/failure.

And yes, you have people that say they have flashed thousands of systems without issue (and, I for one, have flashed at least 3k+ systems in my lifetime, not only PCs but hundreds if not thousands of devices as well), but those of us that have done many also have first hand seen failures of all sorts and have had the pain and anguish of having to attempt to resurrect these failed flashes as well, and a lot of the time under less than ideal circumstances (like systems that NEED to be running for mission critical systems, as it used to happen all the time in server environments, thus those being some of the more "iron clad" flashing systems in the past 20 years).

Also, to clarify Firmwares (like the Intel MEI) are internal "BIOSes" for specific devices (such as the MEI system, thunderbolt subsystem, etc) and a BIOS is a Basic Input Output System that is a specialized firmware for more advanced computing devices (like your motherboard or video card). Just to clarify terminology.

 

Let shall say bios 1.4.4 is the problem which is why it didnt add ME Firmware update.. saying this.. If I flash to a new bios assuming dell will release a new one.. For those laptop with bios 1.4.4 and no updated firmware.. it has more chance of bricking compared to a proper flaahed bios update like what ThomasAAT have.. Did i word it right? lol

 

I assume you will get separate patch instead of full BIOS.