2200 Machine Type And Serial Number Are Invalid Lenovo Laptop
I just replaced the motherboard on my W510 and now when it boots up I get the following errors: 2200: Machine Type Invalid and Serial Number are invalid. 2201: Machine UUID is Invalid After that, it goes on to boot 'normally'.
2200: Machine Type Invalid and Serial Number are invalid (self.thinkpad) submitted 2 years ago by andreas_jacob This is what I'm shown for about 3 sec before normal boot starts. 2200 Machine Type And Serial Number Are Invalid Lenovo Laptops. 7/15/2017 0 Comments. Question How to find a product number or machine type and model? Answer There are many ways! The product number is 7 characters e.g. DJI just made a weird but ultimately sensible announcement. The next firmware updates for all of its drone models will.
My research suggests that a it is possible to 'Fix' this issue with software that's only obtainable by Lenovo field techs. Are there truly no copies of this software anywhere? I can live with it as long as it boots, but it is worrying. I'd rather fix it if possible. Any guidance will be appreciated. It must be easier to find the current nuclear launch codes! With that out of the way, I was able to find version 1.83 and, with Rufus, (thanks for that too) create a bootable usb drive to with which I made the invalid uuid go away.
However, I can't seem to get around the EEPROM write protect error. Pressing escape while the Lenovo logo wes showing had no effect, and when I disabled quick boot and enabled diagnostic boot the Lenovo logo went away altogether. I'm dumped again. What's supposed to happen when I press escape anyway? And what's IBM/Lenovo trying to accomplish by making what should be routine so difficult? Here I thought that replacing the mobo was going to be the hard part!
Do you hit 'esc' one time or multiple times; or do you hold it down continously? The following is going to really date me: As you probably know, making a bootable usb with the utility provided with the HMD doesn't work; it isn't bootable.
M1 garand serial numbers. If you make it with Rufus it's bootable but when it boots, it can't find 'command.com'. That's usually a problem with the MS-DOS 'PATH' command in 'AUTOEXEC.BAT', but 'fixing it' has no effect. I have to manually enter the path to 'COMMAND.COM' which is right in the root directory and shouldn't be necessary.
Howeever, when I do, it boots straight into the utility. However, the 'COMMAND.COM' supplied with HMD is only 9kb, while the 'COMMAND.COM' supplied with Rufus is 90kb??
If I copy over Rufus' COMMAND.COM the AUTOEXEC.BAT fix 'works' but it boots to a C: prompt. A 'DIR/W' command reveals a bunch of files with the two most interesting for my purposes are 'SERUPDT.EXE' and 'SERUPDT2.EXE', both of which have reasonably clear instructions for updating system EEPROM data.
Unfortunately, the error messages I get still suggests that the EEPROM is still write protected. RealBlackStuff wrote:You need to switch off completely (not restart/reboot), if you don't manage to press Escape in time. You should start hitting the Esc button the very moment you press the Power button. If you hit it in time, you should see some messages on your screen, after which it should boot into the HMD program. This Esc is done to remove the write-protect of the BIOS. I'm happy to report I finally got Machine Type/SN replaced.