I'm pretty sure Service tag is part of the BIOS, I didn't look into removing because it hadn't been mentioned. This is something you can set manually in BIOS, when it's not locked in, or change with tools/BIOS edit.
I can probably remove manually I think, and there is tools for that too, that you would run on your end. I think maybe it can be done from either side, you or me

You sent me BIOS for system you said was not committed, and ME info you sent too. Please explain what happened, did you commit or what?
You only had the one system correct, I thought, and then you sent me meinfo and dump BIOS.

What is this BIOS, some other system now? Yes, please explain more, and please update to latest BIOS etc, but do not commit anything, then send that dump.
So all 14x BIOS was waste of time? How is that? Did you have two 7040T systems when you backed up one and it was wrong system?

Do you need this tool, would it help the other system issue?
I think EE-Erase would erase the service tag currently there, and I can find other version I'm sure if this only applies to laptops, which I think this "read me" is from portable package as it mentions.
Also, Dell Client Configuration Utility might help too, but this one below probably best (desktop version though)

Hi

I told you last time that I will receive more Dell optiplex 7040 in stock and I will get also 3040/5040 models.
I received this lot 2 days before and inside this lot was 5 pieces of 7040mt.
I used my old system 7040mt for your Modded bios 25/24 but I didn't saw that this system was already committed because if you can see TAG number that mean it was committed.
I tested all your 25 bios with this system and they all work fine without any problems but didn't test 24 bios.
I cannot confirm 100% that it is working because maybe it is recovering without showing that.
So this is why I used a new system of 7040 to show you how system come before and after it is committed.
You can see a picture which ask us to enter service Tag to commit sustem and select between options. Once we enter all details and apply then system is committed and will run in normal mode and never can change it.
Bios file which I sent to you is before I commit system 7040 in order to keep a virgin copy without TAG and other details.
MeInfo files are for system before and after system was committed like that you can see difference by your eyes.
Now I still have 4 Dell 7040 in office in non-committed mode which I can use to test.
Other commited models I can sell with intel 6th Gen CPU no problem.
Hope you understand me.

Thank you
Salim

Yes, I knew you had more 7040 coming in, but didn't know they were there already. I did not download anything from your previous link, was waiting to figure out what is going on. DST can be removed/reset etc, with special tools, do you need those?
Committed in that since (Dell), is something very different from committed how we think of here with Intel ME/PCH (Dell committed and Intel ME committed are very different things).
I assume you know that, but to keep things clear and understood from us both, moving forward lets not use the committed when talking about Dell with a service tag set, it's confusing and can be undone/reset while ME Committed cannot be undone/reset at all without chipset replacement.

Please send me one single BIOS file you want to use now, for all 7040 moving forward... and we start over I guess?

On the 25 test, that is great all work, then no need to test any of the 24 files toss them out, and there was no need to test further after finding a single one that works, sorry if I did not mention that.
So of the 14 BIOS I sent you, you say 25NoFVME.bin works fine (Does not stop boot, due to Bootguard/ACM), like previous BIOS ME-ucode.bin did? If so, great, that's easy to set while doing ME

Hi

Please note that now I have 5 Dell optiplex 7040 in stock. 4 pieces still in Manufacturing Mode and wz can use to do our tests.

Please find the Bios backup file from a New system which i never used before.

https://fs04u.sendspace.com/upload?SPEED...TINATION_DIR=11


Thank you
Salim

Thanks! Do you need Dell DST tools to clear/change the Dell service tag and any associated ID's etc?
Here, anyway, I posted this tool for another user in case you find useful. If you test and it works on desktop let me know (otherwise I will be finding desktop version shortly I assume for the other user if it fails for him)
Dell Optiplex 3020 BIOS flashing (2)

Also, you never answered me on my last paragraph above in #153, I need to know the answer there before making anymore BIOS.

@simoutekd - Link above is not a working link to download file, please upload again to another host if you can only get long URL's from sendspace (me too right now, not working, valid URL is given on new page in link, short URL) -
site is working for me now, uploading files I mean, then it gives me correct shot linked URL on page refresh for downloads to share. Still unable to download file you linked, that's an interim URL from URL bar you get when uploading, good links to share for uploads will be in middle of page on refresh once upload is done.
Same for package from post #150, those are not sendspace uploaded file links, you have to upload and wait until it's finished, then page will refresh and link to share will be in middle of page

I have Kaby Lake CPU on the way now!

Please can you tell me which question you need me to answer.

If this one @So of the 14 BIOS I sent you, you say 25NoFVME.bin works fine (Does not stop boot, due to Bootguard/ACM), like previous BIOS ME-ucode.bin did? If so, great, that's easy to set while doing ME@

Yes I tested all 25 Bios files you sent to me and all started without any problem and windows is working perfectly.
I didnt receive any notification on screen when computer started.

Hope this is what you need.

This is file you asked for.
Let me test your tool on Desktop.

https://www.sendspace.com/file/sog9o6


salim

Sorry for not saying what question exactly, but yes you got it correct. That's great, my first edit was the right one then, and 13x others were unnecessary [smoking]

I will find the desktop version, please try that one I linked above, linked in the other threads, and see if it work on these Dell too (It might).
Thanks for re-upload, I got the file this time

CCTK and DDC is an option too for the service tag resets, but since I do not have Dell systems here I am not sure how easy this is to use
https://www.dell.com/support/article/us/...it-cctk?lang=en
https://www.dell.com/support/article/us/...systems?lang=en

Also, see this, it's old now but may still work on some systems, second download link works I grabbed the file. Then read down for steps to run the service tag utility
https://community.spiceworks.com/how_to/...nspirion-laptop

Also! Bonus from the comments at the above link!

Zitat

---

You CAN use the asset utility to change the service tag. It is an undocumented switch. run asset /s SERVICETAG, where SERVICETAG = the service tag you want to enter.
Works like a charm on Optiplex & Latitude.

---

Here is ATAG_A209 (Asset is included in the previously linked package I uploaded DSTCD, unsure if same or same version) I think all same files in above link too, same CD ISO, but I see ATAG_209 and Asset in CD.ISO are different sizes, so probably different versoins too
https://www.dell.com/support/home/us/en/...?driverid=h3mvy

I also read this about the ISO I uploaded previously, for using ASSET
Usage:
ASSET new_asset_tag Specify new asset tag
ASSET /d Delete asset tag
ASSET /o new_owner_tag Specify new owner tag (if applicable)
ASSET /o /d Delete owner tag (if applicable)

See also, all the Dell belong to YOU open in firefox or FTP app
http://ftp.us.dell.com/utility/

See also, other user here solved his service tag issue manually for one machine (So you can do similar for your one, if none of the above works for you)
Dell Optiplex 3020 BIOS flashing (2)

* Edit @simoutekd - Please test and confirm all OK with this BIOS, bootguard fix applied, ME + Microcodes added (Both this time) + Fit correction - vBIOS next, and doing it right now!
https://www.sendspace.com/file/20jqhv


*Edit - is this the exact system? Asking in regards to checking/updating GOP/vBIOS
https://www.dell.com/support/home/us/en/...desktop/drivers

Also, there is 2018 BIOS there, vs the 2016 one you sent me from dump. Can we update to that, or should we not/wait?

We may run into vBIOS issues , if it's not one thing it's another!!
2016 BIOS dump = vBIOS Intel(R) SKL1043 (2016/5/13) VBIOS X14 for D7/Potomac to fix 0xB2 issue, PB=HDMI, PC=DP, PD=DP - I think it's OK, guide says 1034 and above "Should" support Kaby Lake (Even though kaby not listed in vBIOS data black name, I say?) -
but also, we can update to this one >> SKL/KBL Mobile/Desktop PCI Accelerated SVGA BIOS Build Number: 1046 - I wonder/hope/will find out if those PB=HDMI stuff transfers during update process)

Latest 2018 BIOS = vBIOS Intel(R) SKL1001 (2018/5/10) VBIOS X16 for D7 to fix BITS326748 issue, PB=HDMI, PC=DP, PD=DP - Going backwards? Older version number, new date, larger size than above, maybe this system I linked above is not same system?

See, both have some "Fix Issue" notation, possibly due to exact fix for those mini-systems? We'll find out I guess

Hello

Let me answer your questions.

1- Regarding Dell optiplex 7040 link you sent to me; yes it is the right model I have in office and I can update my bios version to the last one but first I need to insert TAG number or system will not allow me to update Bios version. If you think there is no problem after we insert TAG then I can do it.
2- I will Flash your New Bios file with my programmer tomorrow morning and let you know the final result.
Hope it will work for us this time.

3- Can we do the same with HP AIO or no because I think that SureStart is same like BG or it is using BG as a part of his Routine and just giving a name to it.

Thank you
Salim

We can always change Asset Tag or Service Tag, so that would be OK. But lets go ahead and wait until end, for now we'll use 2016 BIOS you dumped already.

I don't think Surestart is same as Bootguard at all, but it may involve some aspects of it too. I think more inspection is needed on that board, did you try to find other flash rom on there and dump yet?
I will check this though, and send you BIOS to test if I find it's set. We already checked MEInfowin correct, and no measured or verified Boot set on PCH side at end of report? Of course, none of that was set for this Dell systems either, but we still had to fix, so maybe it's possible.
Please check MEinfoWin on one of the HP's, and see at end if measured or verified boot is enabled on the PCH/Left side at bottom of report. If not, then we can disable like the Dell and see if this helps or not.

Hello

How are you?

Today I used your last Bios file you sent to me with my Dell Optiplex 7040MT and it works fine without any problem.

100% working.
I made a new Bios backup with FTP after I powered on my computer with your New bios file just for you to check if there is any problem.
I used MMtool to check file and I can see that there is 2 MC for intel CPU.
I think this time we got it.

Here is a link for you for Bios file after my system started.

https://www.sendspace.com/file/c9lh50

I am just worried about what will happen after we commit system from Manufacturing mode to Normal mode by pressing ALT-F.

Thannk you
Salim

Hey man! Good all is working great now! Next we do vBIOS.
Yes, sorry I thought I mentioned that I went ahead and put both microcodes back in this time around since we found issue was not related to that like we thought previously.

When you commit from manufacturing mode to normal it will be OK, that will be permanently disabled Bootguard/ACM like it is now.
Many systems are shipped this way now, due to manufacturer error or laziness, Bootguard set and Hash/keys put in BIOS, but then PCH burned to no bootguard when committed so waste of time to have key/has in BIOS = same as how we have it all set now.

But, what you mentioned is about Dell system status state, sorry I confused this with ME/PCH Committed this time around. Doing what you mentioned is only going to lock in the service and asset tags and stuff like that, nothing to do with ME Commited state.
No alt + F4 to do this, to commit ME state you will use FPT, once it's time and all testing is done I will have plutomaniac come tell you exactly what do to.

Did you think there is problem? I mean about the FPT backup, why did you send? Only to check? If only that, it's OK, no need to check, if it's 100% OK and normal on your end then we can go ahead with the BIOS files I already have.
If you suspected some issue possibly, please explain more and I will check FPT file.

Tonight I will try to get 2x BIOS done for you, both with GOP/vBIOS change and one with patched PCIE and one without PCIE patched.
Then you test with old CPU, if all OK, then test with Kaby finally!

Ok Good I am not facing any problem with your Bios file and everything worked well with my intel i3-6100.

When testing intel i5-7400 cpu, system dont start. I think it is problem of VBIOS/GOP version.

I am waiting for your New instructions.

I just sent you a copy of Bios after my computer started to check from your side if anything changed inside.

Thank you
Salim

Good, glad all is well! Yes, I don't expect the other CPU to work at all yet Sorry I didn't have time to get you more BIOS yet, will work on that tonight!

Thanks for the reasoning on that BIOS, I assume only changes would be in NVRAM stuff, nothing we need to worry about or check unless you had an issue. I'll try to do the next test round BIOS tonight, promise!

*Edit - @simoutekd - Here is two mod BIOS to test, one with only vBIOS update, but I think that would fail only sending as last resort test.
You should test Dell 7040MT 03102018-ME-uCFIT-vBGOP, this has both GOP and vBIOS updated to Kaby Lake Supported. Make sure booting is OK with old CPU, then once all is good, test with Kaby CPU finally! Fingers crossed!
https://www.sendspace.com/file/15wd5f

Hello

How are you?

I done tests with both Bios files you sent to me and I got;

Both files worked fine with Intel 6th Gen CPU without any problem.

Now regarding Intel 7th Gen cpu, system didnt show anything on screen but Cpu cooler started and also keyboard light is there. I think we are very close but something is missing there.
I tested system with 2 intel 7th Gen CPU; I3-7100 and i5-7400 and getting same results.

I have a suggestion for you,
In our Bios file we used the latest CPUID version CPUID 906E9 for Kaby Lake, Can we use an old Version which is not Final version maybe it will work for us.
Function which is used to identify CPU maybe we should extend it to include Kabylake Address Range. When we added Microcode for Kaby Lake I think we should extend Address because system was with only 1 MC.

CPU Intel i5-7400 SR32W 3.00GHZ X720c918

Thank you
Salim

Good, all still OK! I forgot third BIOS edit maybe needed, PCIE patch, but I will need to research and maybe send PM's to creator on that, since it's made for coffee lake usage I will need to ask/find out hot to change for sky >> Kaby usage.

You are correct, we may need to use other older CPU microcode instead of latest, but hard to know which to use?
Around March/April of 2017 there was platform change/update where 906E9 went from platform 22 (1,5) << Rev 58 (3/9/2017) - to 2A (1,3,5) << Rev 5E (4/6/2017). CPU was released to public (1/3/2017)
In May/June 2017 HT bug for Sky/Kaby was discovered, so should be OK using one before that, I mean at least we know it was being used in motherboards for both CPU's then on same skylake boards.
Or do you think we need to go earlier than March/April 2017? 5E is the bug fix I think. I also see some Z170 using 5E and ME 11.6 updating to 11.8 in Dec 2017, so we may be able to update that later too

Do you have PCIE 80h debug card? If yes, please insert and test again, what debug code does it stop on?
Also, to see if this is possibly still a graphic issue, please test with other old CPU again, turn on windows audio so you can hear windows starting sounds and put volume up high enough so you easily notice.
Then do rest of new checks with Kaby and see if when it's running if windows ever loads to desktop even if you cannot see it.
Also, please run additional check with PCIE and PCI graphics card too if these are on the board, see if you can get graphic output, before we change anything else. << If this OK, then we know vBIOS./GOP issue

It's so hard to find good info on this now, with all the skylake to coffee lake threads/info out there now!

I also consider, maybe the vBIOS needs to have that "Bugfix" stuff, which I checked each setting manually in those vBIOS with Intel BMP tool, and didn't see anything related to what the fixes mentioned nor the "PB=HDMI, PC=DP, PD=DP" correlated to any settings either.