Fault in Update Retriever bios's

The install commands for some bios updates are wrong. The command '%PACKAGEPATH%\winuptp.exe -r' is used but this doesn't work and must be '%PACKAGEPATH%\winuptp.exe -s' as stated here support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-77150 -> look for silent install
I need to change this everytime I look for new bios files.
Examples:
6fuj45u6_6f
ThinkPad BIOS Update for Windows Vista/7 64bit
3.22-1.06
%PACKAGEPATH%\winuptp.exe -r
6fuj45u6_7v
ThinkPad BIOS Update for Windows Vista/7 64bit
3.24.1.06
%PACKAGEPATH%\winuptp.exe -r
6fuj45us_6f
ThinkPad BIOS Update for Windows XP/Vista/7 32bit
3.22-1.06
%PACKAGEPATH%\winuptp.exe -r
6fuj45us_7v
ThinkPad BIOS Update for Windows XP/Vista/7 32bit
3.24.1.06
%PACKAGEPATH%\winuptp.exe -r
6muj31us
ThinkPad BIOS Update US - XP [32], Vista/7/8 [32,64]
1.52.1.21
%PACKAGEPATH%\winuptp.exe -r
7luj28jp
ThinkPad BIOS Update
2.30-1.08
%PACKAGEPATH%\winuptp.exe -r
8auj25us
ThinkPad BIOS Update US - [32,64]
1.44.1.36
%PACKAGEPATH%\winuptp.exe -r
8duj25us
ThinkPad BIOS Update US [32,64]
1.39.1.24
%PACKAGEPATH%\winuptp.exe -r
g4uj20us
ThinkPad BIOS Update US [32,64]
2.57.1.12
%PACKAGEPATH%\winuptp.exe -r
gcuj16us
ThinkPad BIOS Update US [32,64]
2.56.1.13
%PACKAGEPATH%\winuptp.exe -r
Can this be changed at the source?

So no one has any information on how to maintain a clean repository?

Similar Messages

Missing BIOS updates in Update Retriever

Hello,
When I do a search in Update Retriever 5.00.0010 for
Lenovo M92         2121 / Windows 7
Lenovo M82        2929 / Windows 7
Lenovo M82        2756 / Windows 7
A lot of updates is shown, but no Bios Updates , how come? (I'm almost sure that once I was able to see these bios updates, I have tried to rebuilt a new repository, starting from scratch but to no avail)
And searching for Lenovo T61 6458 /windows 7 shows a JP Bios but no US version.
Can anyone confirm that this is a general issue?.
Kind Regards,
Jakob

So no one has any information on how to maintain a clean repository?

Missing driver in Update Retriever / System Update

Hi,
We are missing a driver in Update Retriever for the T540p model:
The driver is also missing in System Update, when we query Lenovo repository directly.
Neither is the driver available for download manually on the support page.
Device 8086:08b2
"Intel(R) Dual Band Wireless-AC 7260"
http://pci-ids.ucw.cz/read/PC/8086/08b2
T540p (20BF-A0FHMD)
BIOS: GMET59WW (2.07) 2014-02-12
ECM: GMHT25WW (1.10)
ME firmware: 9.0.22.1467
Windows 7 pro SP1, x64
Lenovo could you please add this driver to Update Retriever?
Our deployment of this model is pretty much crippled because of this, since we cannot deliver systems without wireless drivers.
Thank you.

dhjensen wrote:
parkerjnc wrote:
We are half way there. It should show up after the next catalog refresh which I'm expecting to happen overnight. Will check it in the morning and escalate if not showing up.
I just checked today and still no luck.
A new version of "ThinkVantage Active Protection System (64bit)" is all i could find for the "3354-Windows 7-English" query
/Daniel
I will correct that. We had approved our own "Costum update" with the same update id. After removing that the update appeared as exspected.
Thank alot for being very helpfull.
/Daniel

L440 System Update / Update retriever Differences/Issues

I have Got some issues on the L440 model using Update Retiver / Thin Installer model is . (20AS)
Update retriever is not showing the following that system update shows
Thinkpad power manager v6.64.2
BIOS update
Update retriever does show
Intel WLAN Driver - 7[64] V16.10.0
But thininstaller does not show this when run on the machine!!!
It Also has problem installing
Intel SATA Controller AHCI Driver - 7/8[64] - V12.8.1.1000
Warning 2014-03-03 , 03:15:26
at Tvsu.GenericPackageInstaller.InfInstaller.InstallUpdate()
Message: An error ocurred trying to install Intel SATA Controller AHCI Driver - 7/8 [64] update
Can anyone help with this ?

Can you do another search through UR and see if the missing content is showing up now? We had some issues with the power managment driver and also the Intel WiFi driver packages. There is a new Intel WiFi package that targets properly to all the supported models. You will see in UR one package that can be used for intial installation on all models and one package that should be used for upgrading a previous driver for non-7260 cards. If you are doing deployments of new systems just get the first one.

TVSU & Update retrieve & ThinInstaller

Hello -
I have two models T420(4178) and the X220(4287) and I'm trying to use TVSU and/or Update retriver with ThinInstaller.
With the TVSU the update for ThinkVantage Active Protection System (32 bit) does not show up as a required update.
With Update retriver I can download the update "ThinkVantage Active Protection System (32 bit)" but when I run the Thinistaller agaianter that repository it is not being deteceted as a needed update.
This is on both machines that are Windows 7 32 bit.
I'm under the impression that any updates I download into the Update retriever repository will be available and installed when ThinINstaller runs.
thanks for any help you can provide.
Solved!
Go to Solution.

There is a work around that you can use to update Thin Installer so it will properly handle the APS package for T420, X220, etc. The BIOS updates for these systems have been released to the web and we are working on getting them to show up for TVSU and TVUR. Hoping that happens next week.
Workaround to update Thin Installer for APS:
1.   In Update Retriever, either do a "Get new updates" or search your repository for a Critical update titled "System Update Patch [Fix multi must-reboot QFE packages install issue and APS device detection issue] for Windows 7"
2. Once this package is downloaded into your repository, go to Windows Explorer and open your repository folder
3. Go to the su_multiqfe_aps_w7 folder
4. Manually execute su_multiqfereboot_aps.exe from this folder
5. Follow the wizard up to the last panel with the Finish button.
6. !!! Uncheck the checkbox and then click Finish. This will export the package to the
    c:\SWTOOLS\DRIVERS\SUPATCH_MULTIQFEREBOOT_APS\su_multiqfereboot_aps\ folder.
7. In the folder generated by step 6 you will find two .sys files: tvsuhd64.sys and tvsuhd32.sys. Replace the older files in the Thin Installer set of files with these newer ones.
Now this set of Thin Installer files can be used to install APS on the new systems.
NOTE: Make sure your Thin Installer command includes the parameter -includerebootpackages 3    The APS package is a type 3 so that needs to be specified or else Thin Installer will skip it.

Satellite 1410-604 - BIOS update Incorrect BIOS update in the web?

Hi there again!
Now with a new and weird matter.
We all know that old say... "If it is not break, don't fix it". And if you put it into more informatic terms, "specially if it is a BIOS".
Yes, we all know that the BIOS is something quite dellitate to handle. For some reason we normally feel like if we were handling something like nitro-glycerine, or some radioactive product. And this is because we all know what is being put in risk in that moment: our (or sometimes others) computer, the full system could end as dead as some pieces of metal, plastic, and wires.
Well. I passed through all of that more than ten times in my life, and only once it went wrong. But since that old motherboard was already dead, It was not important. But I allways was EXTREMELY care. I allways cross checked everything before doing anything, allways got a backup and a way to restore that backup... and allways did this in COMPAQ systems, that were prepared that way. Updating a BIOS was just about preparing a disk, turn on the PC with the disk in the diskette drive, and wait. And if you didn't like the results, you simply click "return to previus BIOS" and that was it... very nice. And easy.
Few days ago, a friend brought me a Toshiba Satellite 1410-604 to solve some issues that were driving him crazy. After removing an expired Norton Internet Security, install avast and scan, I found more than one hundred files infected with a wide variety of virus, malware, trojans, and whatever you could imagine. Avast removed them all, but the remains of the operating system was so unstable that we decide to format and install from scratch.
I asked for the restoration disks, that obviously he don't have because they were lost in one of his movings. After we got the confirmation from Toshiba reps that there are no recovery disk available for this model, because it is too old, we decided to install from scratch like any other normal PC, and resigned to loose some of the utilities that come with that CDs and that are not available for download in the website.
I downloaded all of the software available for this model, including two BIOS updates. (Actually only one update, but in two versions: Windows and Traditional), and prepared a CD with all the drivers and programs just like if it were a brand new system install. And everything went very well, no problems at all. Until we got to the Wireless LAN card, but that is another issue that is already solved (the mini PCI card for the WLAN does not support WEP or WAP encription, and it is not possible to connect to any wireless LAN encripted).
At this point, and when I started configuring and enabling PCMCIA devices, and USB devices (this computer only supports USB 1.1 not 2.0) I discovered this text in the Toshiba Website:
"This Bios Update adds increased functionality to your system.
(BIOS is an acronym for Basic Input and Output System. This program is stored in a Read-Only Memory chip on the motherboard.
When the computer powers up, the BIOS is launched to perform various start-up functions.)
For detailed update information please refer to Toshiba BIOS-Update Information"
(you can find this here:
[http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU] you have to look for:
Archive
Satellite
Satellite 14xx
Satellite 1410-604
PS141E
Quite specific. Isn't it?)
According to the information in that same website, the BIOS available fits the following models:
"Satellite 2410-414, Satellite 1410, Satellite 1410-654S, Satellite 1410-814, Satellite 2410-303, Satellite 2410-304S, Satellite 1410-354, Satellite 2410-601, Satellite 1410-401, {color:#ff0000}*Satellite 1410-604*{color}, Satellite 2410-404, Satellite 1410-301, Satellite 1410-304, Satellite 2410-S403, Satellite Pro 2100, Satellite 1410-S203, Satellite 2410-304, Satellite 1410-554, Satellite 1410-S102, Satellite 1410-354E, Satellite 2410-703, Satellite 1410-303, Satellite 2410-S203, Satellite 1410-801, Satellite 2410-603, Satellite 1410-902, Satellite 1410-313, Satellite 1410-802, Satellite 1410-714, Satellite 2410-354, Satellite 2410-514, Satellite 1410-614, Satellite 1410-704, Satellite 2410-515, Satellite 2410-504, Satellite 2410-702, Satellite 1410-S103"
Yes... it's there!
Now, when you go to the "Toshiba BIOS-Update Information", you get:
"FAQ Ref.: TRO0000000b07
A BIOS update is a {color:#ff0000}*relatively simple operation and can be carried out by most competent computer users*{color}. All BIOS upgrades can be obtained from "BIOS Update" Download Section click here..
Note: The BIOS files are machine specific so the correct BIOS for your machine must be used."
Please note that Toshiba does not disencourage the handling of BIOS, on the contrary: they even encourage people to do so. This is not necessary bad, but at the same time they encourage people to 'play around' with such a delicate matter, at the end of that same page, in little letters they say:
"Toshiba provides this information "as is" {color:#ff0000}*without warranty of any kind*{color}, either expressed or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Toshiba shall not be responsible for the topicality, correctness, completeness or quality of the information provided. {color:#ff0000}*Toshiba is not liable for any damage caused by the use of any information provided, including information that is incomplete or incorrect*{color}."
This should trigger yellow alarms in our minds.
+"Human error is inherent to humans, and it is not possible to erradicate. It will allways appear, sooner or later" (Prof. James Reason).+
And finally I made the mistake. Even though I read that warning, I remembered all those successfull BIOS update with COMPAQ, and relied in Toshiba. That update was available there, and Toshiba was telling me that it was for this computer. Great!
So finally I unplugged all devices (USB), removed the PCMCIA (WLAN),plugged the battery charger to avoid any possible battery problem, restarted windows, and then from within windows I started the updater (windows version, as recommended by Toshiba). Everithing looked fine, nothing different of what I used to see on those old COMPAQs.
As warned by the updating program, the system was going to reboot. And actually it did so.
Windows closed quite normally (a bit quicker than normal, but without errors, and since there were no other programs than the essentials -even the antivirus was not running-), the computer switched of, all lights off (normal), and then it switched on again...
{color:#0000ff}*BEEEEEEEEEEEEP... BEEEP... BEEEEP...*{color}
OMG! I never espected something THAT bad. 3-1-1!
And now... What a 3-1-1 stands for here? Award BIOS would mean no video card or deffective video card, but it is not true, since it was working up to 20 seconds ago. It must be the BIOS.
It never came again to life. It is still beeping 3-1-1.
But now comes the investigation of the human-factors involved in this accident.
I found I commited the following failures:
*(1)* To rely in the manufacturer, even though they WROTE their information could be wrong or incomplete. (BAD if I were a QA&QC inspector).
*(2)* I didn't cross checked deeply enough (until it was already too late).
*(3)* I didn't looked previously for the way to make a backup of the BIOS, in order to restore should anything go wrong.
*(4)* Let Toshiba lead me to a path I didn't want to walk, just because of their offer of "increased functionality".
*(5)* Beleave in Toshiba when they said "relatively simple operation and can be carried out by most competent computer users"... they never said it is failproof.
Then I started the most interesting part of the investigation.
{color:#0000ff}*"What went wrong?"*{color}
Obviously, the BIOS update failed somehow, somewhere. And I wanted to know what and where.
First thing I discovered was that there are another search engine in Toshiba called "askiris" ([http://askiris.toshiba.com]) and I looked there in order to see if for any chance I could get the old 1.20 BIOS version that was installed originally in that machine.
And I found something... VERY interesting:
bq. {color:#800080}*From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* bios for these models. TAIS. Downloads. DL. 105481 289838 289838 ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410. 2002-10-04. 105589...* \\ {color}{color:#800080}* Published 10/4/02* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415* \\ {color}{color:#800080}* FDD Version 1.30 TAIS. Downloads. DL. 105481 357972 357972 ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415. 2003-01-31. 105589 PUB...* \\ {color}{color:#800080}* Published 1/31/03 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.20 for Satellite 1410/2410* \\ {color}{color:#800080}* error message during BIOS TAIS. Downloads. DL. 105481 305240 305240 ACPI Flash BIOS version 1.20 for Satellite 1410/2410. 2002-11-01. 105589 PUB...* \\ {color}{color:#800080}* Published 11/1/02 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* 1) Changed the content TAIS. Downloads. DL. 105481 330963 330963 ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410. 2003-01-03. 105589...* \\ {color}{color:#800080}* Published 1/3/03 | Rating:* {color}
Those are: V110, V140, V120 and V130 for series 1410/15 and 2410.
GOOD! Or not?
Let's take a look:
First thing I did was download everything all four files.
Then I took the same version that made the crash: 1.40
Than I uncompressed the file, and I found:
06/05/2009 00:17 <DIR> .
06/05/2009 00:17 <DIR> ..
31/01/2003 08:38 1,605,632 11410v14.iso
31/01/2003 08:38 511,764 1370D14.EXE
{color:#ff0000}*08/01/2003 17:03 724,480 2410a9v140.exe*{color}
09/01/2003 09:32 250,663 biofca9t.com
08/10/2002 05:26 30,697 chgbiosa.exe
31/01/2003 08:36 1,087 instinfo.bat
13/05/2002 15:25 378,175 launcher.exe
31/01/2003 08:36 433 launcher.ini
06/05/2009 00:17 0 list.txt
31/01/2003 08:36 14,768 readme.com
*{color:#ff0000}31/01/2003 08:36 12,513 readme.txt{color}*
11 archivos 3,530,212 bytes
3 dirs 9,404,600,320 bytes libres
And I got my first surprise here: There is a {color:#ff0000}*README.TXT*{color} that was not present in the file I downloaded previously from the drivers repository.
So I went to the readme.txt and I found this:
"README.TXT 01-31-2003 CDC
Flash BIOS version 1.40 for Satellite 1410
This BIOS is applicable to the following models:
Satellite 1410-S105
Satellite 1410-S106
Satellite 1410-S173
Satellite 1410-S174
Satellite 1410-S175
Satellite 1410-S176
Satellite 1415-S105
Satellite 1415-S106
Satellite 1415-S115
Satellite 1415-S173
Satellite 1415-S174
Satellite 1415-S175
Satellite 1415-S176
Satellite 2410-S203
Satellite 2410-S204"
Please note that the model 1410-604 is *NOT* listed.
I thought "well, it must be another archive..."
But then I realized of a name that sounds familiar, it was there, in the directory where I uncompressed this 1.40 file, and the name is:
{color:#0000ff}*2410A9V140.EXE*{color}
So I took the other file, the BIOS_Win update, and I discovered that the file name is:
*{color:#0000ff}2410A9V140.EXE{color}* (Ups!)
So I uncompressed it again, to find:
El volumen de la unidad D no tiene etiqueta.
El n£mero de serie del volumen es: 8838-E175
Directorio de D:\Shared\diskette\2410A9v140
06/05/2009 00:43 <DIR> .
06/05/2009 00:43 <DIR> ..
*{color:#0000ff}09/01/2003 09:32 _250,663_ BIOFCA9T.COM{color}*
17/07/2002 03:38 35 biosupd2.ini
13/07/2001 13:22 6,277 chgbios2.vxd
*{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
09/11/2001 09:14 134 clean2.reg
17/07/2002 03:35 342,064 install2.exe
16/07/2002 06:55 241,664 nchgbios2.exe
18/08/2001 11:41 3,435 nchgbios2.sys
23/10/2001 18:55 11,476 nchgbios2NT.sys
26/08/2001 09:00 49,152 nchgbios2svc.exe
13/07/2001 17:05 49,152 tbdecode.dll
14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
21/06/2002 11:25 1,796 tosclean2.bat
09/11/2001 12:01 967 tosclean2.pif
21/06/2002 11:34 1,841 toscleanAUTO2.bat
21/06/2002 11:44 1,796 toscleanSMS2.bat
21/06/2002 08:51 2,038 tosntclean2.bat
21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
21/06/2002 08:52 2,038 tosntcleanSMS2.bat
20 archivos 1,046,461 bytes
2 dirs 9,402,793,984 bytes libres
No readme file...
Then another question arised in my mind: What about the other 1.40 file? What does the other 2410A9V140.EXE have inside?
This:
El volumen de la unidad D no tiene etiqueta.
El n£mero de serie del volumen es: 8838-E175
Directorio de D:\Shared\diskette\comparacion_toshiba\askiris\241 0a9v140
06/05/2009 00:46 <DIR> .
06/05/2009 00:46 <DIR> ..
*{color:#0000ff}09/01/2003 09:32 _250,663 _BIOFCA9T.COM{color}*
17/07/2002 03:38 35 biosupd2.ini
13/07/2001 13:22 6,277 chgbios2.vxd
*{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
09/11/2001 09:14 134 clean2.reg
17/07/2002 03:35 342,064 install2.exe
16/07/2002 06:55 241,664 nchgbios2.exe
18/08/2001 11:41 3,435 nchgbios2.sys
23/10/2001 18:55 11,476 nchgbios2NT.sys
26/08/2001 09:00 49,152 nchgbios2svc.exe
13/07/2001 17:05 49,152 tbdecode.dll
14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
21/06/2002 11:25 1,796 tosclean2.bat
09/11/2001 12:01 967 tosclean2.pif
21/06/2002 11:34 1,841 toscleanAUTO2.bat
21/06/2002 11:44 1,796 toscleanSMS2.bat
21/06/2002 08:51 2,038 tosntclean2.bat
21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
21/06/2002 08:52 2,038 tosntcleanSMS2.bat
20 archivos 1,046,461 bytes
2 dirs 9,402,781,696 bytes libres
*{color:#ff0000}They both have 20 files, and 1,046,461 bytes. I asumed they are both the SAME file{color}*.
And the readme file does not list the model 1410-604 in its readme file, therefore I cannot explain this except as a mistake from Toshiba. *{color:#ff0000}They put an incorrect BIOS in their website, and suggested the update, and somehow leaded to this kind of errors.{color}*
(Except in the case that one of those models is a different name of the 1410-604 model, and if it is the case... now I don't know why this BIOS do not work with this computer).
The worst part is that neither of those other files (V1.10, 1.20 and 1.30) lists the 1410-604, therefore there seems no possible workaround for this problem. I need an original v1.20 for this CMOS, and Toshiba seems not to have it. They offered me to solve the problem, by leaving the notebook at an ASP, and paying only 95€ for the work and about 280€ for a motherboard replacement, I will get it solved. But they offer no warranty of their possibilities because is a model 'too old' and 'discontinued' and with 'no support'...
In other words, they said "don't bother with this, just go out there and buy a new one" (something absolutely out of my scope in this crisis-time) :P
Thank you for reading soooo far.
Now what I need is to get any ideas of a workaround for this, my ideas are:
(1) This CMOS has a boot-part that still works (it allows a roll-back if you have the appropriate file). So I need a good BIOS to burn into the CMOS, from the VERY SAME model (a BIOS backup) but the backup must be adequate for the burning program (CHGBIOSA.COM).
(2) It is still possible that the BIOS could be OK but the data on the CMOS got somehow corrupted. If so, clearing the CMOS could solve de problem. But I was not able to find a clear cmos button from outside, and after disasembling I took of the battery, with no good results. I have to try leaving the MOBO without battery for longer period (I left it about 20 seconds) just in case 20 seconds don't allow all the capacitors to fully go to zero values. I have not much hope in this point.
(3) Try to get a REAL good update from Toshiba. I contacted several times technical support, and I was able to verify they are only phone-operators, with a script in front of them, and when the problem goes-out-of-scope they fall always in the same answer: "you have to go to an ASP". I still have a low hope to find someone who really knows a bit, and could enlighten with a good BIOS to put in this disks.
(4) As far as I could find, this BIOS is not from any known BIOS-maker. It seems it has been developed by Toshiba (own brand), therefore the Crisis Recovery Disk from Phoenix will not be of any help here. As well as any other BIOS recovery tool not designed for Toshiba's BIOS. But I'm open to any ideas, that could be tested more or less safely. (Remember that the 'BIOS-BOOT-PART' feature is still working, I don't want to loose this only possibility of redemption).
Wwwaaaaoooowww... what a long-post falks! Sorry for that!
Forgive me, but I wanted to be really clear.
Should anyone give some hints or advice, will be greatly appreciated.
Please don't say what I shouldn't do... I already know that. I already researched and already found my mistakes, in order not to repeat them. Now I need to move on, to advance, and to try to solve this, or at least learn how to solve similar things. As much as possible.
Thank you again, in advance, and sorry again.
FenixDigital
Message was edited by: Fenix_D
Changed subject to beter reflect what is the matter about (apparently erroneous BIOS file in Toshiba download center).

Well. 
 
It's not dead, certainly. 
 
The steps that I put in my procedure were: 
 
--> There are two memory sims, that I am going to identify as M1 and M2 
--> There are two memory banks, that I am going to identify as A and B 
 
Next step in order to identify if there are some module or bank that is not working properly are: 
 
The modules were installed as: 
 
M1 --> A 
M2 --> B 
 
1--> Boot without any memory chip. 
 
<blockquote>
A--> X 
B--> X 
</blockquote>
 
2--> Boot with ONE module 
 
<blockquote>
A-->M1 
B-->X 
</blockquote>
 
3--> Boot with the OTHER module 
 
<blockquote>
A--> X 
B--> M2 
</blockquote>
 
4--> Boot with BOTH modules swapped: 
 
<blockquote>
A--> M2 
B--> M1 
</blockquote>
 
5--> Boot with ONE module swapped: 
 
<blockquote>
A--> M2 
B--> X 
</blockquote>
 
6--> Boot with the OTHER module swapped: 
 
<blockquote>
A--> X 
B--> M1 
</blockquote>
 
At this point I got a great difference. It booted, finally. But in order to make a diagnostic, I have to complete the full test, and the results were: 
 
1--> Boot without any memory chip. 
 
A--> X 
B--> X 
 
NOT BOOTING Actually the computer not even tries to read the disk. Only the power led turns on, but even prior to press the 'on/off' button. I think this indicates 'no memory installed'. I would have expected a post failure beeps, but there were no beeps at all. 
 
2--> Boot with ONE module 
 
A-->M1 
B-->X 
 
BOOTED NORMALLY Well. This obviously means that the 3-1-1 beep code means memory error, or one bank failing of two installed. Now I didn't know if the problem was the module, or the bank B. 
 
3--> Boot with the OTHER module 
 
A--> X 
B--> M2 
 
NOT BOOTING Just like the condition in 1. Like no memory installed, therefore there are two possibilities: The bank B is not working, or the memory module M2 is not working. 
 
4--> Boot with BOTH modules swapped: 
 
A--> M2 
B--> M1 
 
NOT BOOTING Just like previous to test condition. Beep code 3-1-1, no boot at all. 
 
5--> Boot with ONE module swapped: 
 
A--> M2 
B--> X 
 
NOT BOOTING This was the important test, because it finally let me determine that the problem is at the module 2 (M2) not at the bank B. But still there could be a failure IN THE BANK B and IN THE MEMORY MODULE 2. Have to do the other test. 
 
6--> Boot with the OTHER module swapped: 
 
A--> X 
B--> M1 
 
BOOTING NORMALLY This really confirmed there is nothing wrong with ANY bank, but one of the modules is not working, actually is not being even detected. This is quite weird, because this computer was working perfectly with those two modules, and in the moment of the BIOS upgrade it seems to fail... How come? 
 
Something weird happened here. I don't know what, but something ruined one memory module (fortunately only one), what I would like to know now is what happened. But at least I have the machine running, with very low memory, but running. 
 
What I am thinking now is what about this BIOS upgrade makes the motherboard not to recognize one of the modules for some reason? 
 
<img class="jive-emoticon" src="images/emoticons/happy.gif" border="0" alt=":)" /> 
 
I will continue my research, but certainly the memory made the difference. 
 
I am not sure why I didn't discover this before, I think I didn't perform this test before, for two reasons: 
 
(1) I tried to boot with no memory, and this was impossible, so I assumed that the problem was not at the memory. 
 
(2) When I heard the beep code (3-1-1), somewhere I read it was a video problem, and I asume most probably it was a video problem (since no video at all was being displayed) but I should have take into consideration that Phoenix BIOS also means with the same 3-1-1 a DMA problem (memory problem). 
 
Okis... It's a pitty having to wait so much between a post and it's approval. I posted my answer two days ago, and since it didn't appear, I believe It didn't upload, so I replied again, and also didn't appeared... until now. It is obvious that a moderator approval is required. That's why I have to wait 24 hours or more to read my post. This slows this forum effectiveness. 
 
Thank you very much for your help. I'll keep you informed. Until we get to a final diagnosis and solution.

X230 Family Type 2325 drivers In update retriever

Hey,
I've been using UR for quite some time and it's working great for me with SCCM etc.,
the organization I work for had began purchasing X230 family laptops (Type 2325),
I'm missing some drivers from Update Retriever that are available on the support website,
I'm searching for type 2325 language English OS Windows 7
these are:
ThinkPad Bluetooth g4wb10ww (Version 6.5.1.2700) (appears as BCM... In device manager)
RapidBoot Shield 32/64 (both appear on UR but fails to download while all other drivers successfully download from UR)
USB3.0 Appears but doesn't seem to get installed (it appears In candidate list log of thininstaller),
then I read that on the RapidBoot shield update notes that usb 3.0 needs rapidboot drivers v1.23 (which doesn't appear on the new driver releases page:
http://support.lenovo.com/en_IL/research/hints-or-tips/detail.page?DocID=HT050904
Software name RapidBoot Shield
Support models ThinkPad(R) L330
ThinkPad L420, L421, L430
ThinkPad L520, L530
ThinkPad T420, T420i, T420s, T420si, T430, T430i, T430s, T430u
ThinkPad T520, T520i, T530, T530i
ThinkPad W520, W530
ThinkPad X1, X1 Hybrid, X1 Carbon
ThinkPad X121e, X130e, X131e
ThinkPad X220, X220i, X230, X230i
ThinkPad X220 Tablet, X220i Tablet, X230 Tablet, X230i Tablet
ThinkPad V490u
ThinkPad Edge E120, E125, E130, E135
ThinkPad Edge E220s
ThinkPad Edge E320, E325, E330, E335
ThinkPad Edge E420, E420s, E425, E430, E435
ThinkPad Edge E520, E525, E530, E535
ThinkPad Edge S430
Lenovo(R) V480, V480s
Lenovo V580
Lenovo B475e, B480, B480r, B485, B490
Lenovo B575e, B580, B580r, B585, B590
Zhaoyang K29, K49, E49
Lenovo E49
Operating Systems Microsoft(R) Windows(R) 7 32-bit, 64-bit
Refer to marketing materials to find out what computer models
support which Operating Systems.
Version 1.23
WHAT THIS PACKAGE DOES
RapidBoot Shield is a utility that reduces the boot complete time of PC running
Windows 7 operating systems.
If this package has been installed, updating (overwrite-installing) this
package will fix problems, add new functions, or expand functions as noted
below.
CHANGES IN THIS RELEASE
Version 1.23
[Important updates]
Nothing.
[New functions or enhancements]
- Changed the software name from RapidBoot to RapidBoot Shield.
[Problem fixes]
- Fixed an issue that the desktop window becomes dark and mouse is unresponsive
when SimpleTap is launched during boot time.
- Fixed an issue that RapidBoot does not work after upgrade install on Win7 64-bit
operating system.
- Fixed an issue that mouse cursor intermittently becomes unresponsive for a while.
- Fixed an issue that RapidBoot delays keyboard response during Lenovo Setup(OOBE).
- Fixed a 0x9F BSOD issue that occurs intermittently.
[Note] If you plan to install Intel USB3.0 driver 1.0.4.225 or newer version,
please install Rapid Boot Shield first.
from the log(1st run):
Info 2012-07-01 , 02:32:56
at Tvsu.Coreq.LoadCoreqsProcessor.ProcessUpdatesImplementation(Update[] ups)
Message: Candidate list:
Integrated Camera Driver for Windows[reboot type 3]
WiDi driver for Intel cards for Windows 7 64bit[reboot type 3]
ThinkPad Wireless LAN (11b/g/n)[reboot type 0]
Lenovo Mobile Broadband Activation[reboot type 0]
WiMAX Driver for Intel Cards (For Windows 7 32bit)[reboot type 3]
ThinkVantage Active Protection System[reboot type 3]
Realtek Audio Driver for Windows 7 32/64[reboot type 3]
ThinkVantage GPS[reboot type 0]
WiDi driver for Intel cards for Windows 7 32bit[reboot type 3]
Ericsson H5321 Wireless WAN Driver for Windows[reboot type 0]
WiMAX Driver for Intel Cards (For Windows 7 64bit)[reboot type 3]
ThinkPad Power Manager[reboot type 3]
Intel AMT 8.0 - MEI and SOL driver[reboot type 3]
ThinkVantage Active Protection System[reboot type 3]
ThinkPad UNDP Wireless WAN Driver(Gobi3000)[reboot type 3]
Sierra Wireless MC7750 - Gobi 4000 (TM) Softwaree[reboot type 3]
Media Card Reader Driver for Windows XP/732/764 - WW -[reboot type 3]
ThinkPad Power Management Driver[reboot type 3]
Intel PRO/1000 LAN Adapter Software for Windows XP 32-bit, 7 32-bit[reboot type 0]
ThinkPad Hotkey Features Integration Package Setup[reboot type 3]
Fix for Issue of HDD with HDP Detection for Windows Vista/7[reboot type 0]
ThinkVantage Access Connections for Windows 7[reboot type 3]
WiFi driver for Intel cards For Windows 7 64bit[reboot type 3]
Intel USB3.0 eXtensible Host Controller[reboot type 3]
WiDi Driver for Intel Cards for Windows 7 32/64bit[reboot type 3]
Intel Rapid Storage AHCI Driver for Windows 32bit[reboot type 3]
Intel PRO/1000 LAN Adapter Software for Windows 7 64-bit[reboot type 0]
Intel HD Graphics 2000/2500/3000/4000 Display Driver for Windows 7 64bit[reboot type 3]
WiFi driver for Intel cards For Windows 7 32bit[reboot type 3]
Intel Chipset Support for Windows XP/Vista/7[reboot type 3]
Intel HD Graphics 2000/2500/3000/4000 Display Driver for Windows 7 32bit[reboot type 3]
ThinkVantage Communications Utility[reboot type 3]
Info 2012-07-01 , 02:32:56
at Tvsu.Coreq.LoadCoreqsProcessor.ProcessUpdatesImplementation(Update[] ups)
Message: Resulted order of candidate list:
Intel HD Graphics 2000/2500/3000/4000 Display Driver for Windows 7 32bit[reboot type 3]
Intel Chipset Support for Windows XP/Vista/7[reboot type 3]
Intel HD Graphics 2000/2500/3000/4000 Display Driver for Windows 7 64bit[reboot type 3]
Intel PRO/1000 LAN Adapter Software for Windows 7 64-bit[reboot type 0]
Intel Rapid Storage AHCI Driver for Windows 32bit[reboot type 3]
Intel USB3.0 eXtensible Host Controller[reboot type 3]
Fix for Issue of HDD with HDP Detection for Windows Vista/7[reboot type 0]
Intel PRO/1000 LAN Adapter Software for Windows XP 32-bit, 7 32-bit[reboot type 0]
Media Card Reader Driver for Windows XP/732/764 - WW -[reboot type 3]
Sierra Wireless MC7750 - Gobi 4000 (TM) Softwaree[reboot type 3]
ThinkPad UNDP Wireless WAN Driver(Gobi3000)[reboot type 3]
ThinkVantage Active Protection System[reboot type 3]
Intel AMT 8.0 - MEI and SOL driver[reboot type 3]
Ericsson H5321 Wireless WAN Driver for Windows[reboot type 0]
ThinkVantage GPS[reboot type 0]
Realtek Audio Driver for Windows 7 32/64[reboot type 3]
ThinkVantage Active Protection System[reboot type 3]
Lenovo Mobile Broadband Activation[reboot type 0]
ThinkPad Wireless LAN (11b/g/n)[reboot type 0]
Integrated Camera Driver for Windows[reboot type 3]
ThinkPad Power Management Driver[reboot type 3]
ThinkPad Hotkey Features Integration Package Setup[reboot type 3]
ThinkPad Power Manager[reboot type 3]
ThinkVantage Access Connections for Windows 7[reboot type 3]
ThinkVantage Communications Utility[reboot type 3]
WiFi driver for Intel cards For Windows 7 64bit[reboot type 3]
WiMAX Driver for Intel Cards (For Windows 7 64bit)[reboot type 3]
WiFi driver for Intel cards For Windows 7 32bit[reboot type 3]
WiDi driver for Intel cards for Windows 7 64bit[reboot type 3]
WiMAX Driver for Intel Cards (For Windows 7 32bit)[reboot type 3]
WiDi driver for Intel cards for Windows 7 32bit[reboot type 3]
WiDi Driver for Intel Cards for Windows 7 32/64bit[reboot type 3]
Info 2012-07-01 , 02:32:56
at Tvsu.Coreq.CoreqProcessor.ProcessUpdatesImplementation(Update[] updates)
Message: Beginning Coreq process: Recieved 32Updates
on the 2nd run:
WiDi Driver for Intel Cards for Windows 7 32/64bit[reboot type 3]
WiDi driver for Intel cards for Windows 7 64bit[reboot type 3]
ThinkVantage Communications Utility[reboot type 3]
ThinkVantage GPS[reboot type 0]
Solved!
Go to Solution.

Sorry for these issues, the updates team is still working on getting all the updates published for the new systems like X230...
Bluetooth should be there starting from today.
I recommend not installing RapidBoot Shield unless you have personally tested it and determined that it makes your image boot faster and doesn't cause side-effects.
Intel USB 3.0 has a wrong dependency on RapidBoot Shield, the team is working on removing the dependency. If you are using ThinInstaller you may be able to figure out how to remove the dependency from the XML file yourself...

How can I update the BIOS without using a CD?

Hello!
I have recently decided to upgrade my RAM from 2GB to 4GB. After installing, I booted up my computer to find that it would not recognize the new memory. After doing a bit of troubleshooting, I decided to try and update the BIOS, as the version was from 2010. I downloaded the BIOS update boot CD application from lenovo, burned a disc, and on reboot I found that the boot order did not have CD listed on it. Here's the catch: I don't have the supervisor password. This is a hand-me-down laptop, and I have tried to find the password to no avail. This is the current boot order: USB drive, Hard drive.
My question is, can I either create a BIOS update disc using a USB, or update the BIOS some other way?
I understand that it is impossible to recover the supervisor password without having it serviced (which I would rather not do, even if I have to send my RAM back to Crucial)
My system specs:
Thinkpad L512
Bios version: 1.04
Bios date: 2010-3-26
Embeded Controller Version: 1.01
Windows 7 32 bit
Thanks for your help.
Solved!
Go to Solution.

Welcome to the forum!
Two things here:
a) If you run System Update, it should offer the latest BIOS for your machine as well. I've never done it on a passworded unit, so it might or might not work but might be worth a shot.
b) I doubt that the ability of the system to recognize new RAM has anything to do with the BIOS. ThinkPads much older than yours will run 4-8GB RAM with an old BIOS, older than your machine to begin with.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

Z97 MPOWER MAX updated to BIOS 1.9 and no boot/ C9 error

After updating to BIOS 1.9 from 1.8, I am finding that my systems hangs (nothing displayed on screen, cannot enter BIOS) with post code 9C displayed. For no reason I can understand, sometimes is hangs like this for 5-10 boot attempts. If I come back after 1 h or so, it mysteriously boots with no problems. I found that this is a USB init problem. I don't want to move these to USB 3.0 ports which some have suggested in other threads simply because I have never experienced this under BIOS 1.8. What settings in my BIOS can I change to make boot up reliable?
I have a USB mouse and keyboard connected to the USB 2.0 ports, but that's it for USB devices.

Quote from: Svet on 05-June-15, 17:35:37
what are the models of your USB mouse and keyboards?
and can you figure which one of them is cause this hang?
have you done >>Clear CMOS Guide<< with power cord removed after flashing the new bios?
Thanks for the reply. The keyboard is a micro$oft natural 4000 and the mouse is a kensington "mouse-in-a-box" optical (model 72112). Next time it hangs I will disconnect them one-at-a-time to see if I can figure which might be to blame. I have not cleared the CMOS with the power cord removed, just flashed, unplugged the power for 2 min, reloaded defaults, and then modified to my liking.

Home Environment - How to set up Update Retriever (UR) and Thin Installer (TI) in a home environment

Serenityvalley wrote:
You need to go to This Page and download just about everything on it -espeically the System Update Deployment Guide and start reading. It'll take you a few hours to learn what you need to do and implement it if you are familar with editing system registeries and you have some luck and everything goes well.
You do NOT need to edit registry, just use Thin Installer instead of System Update on the clients. And there is no need to wade thru the deployment guide if you are setting this up in a home environment for just one or two clients.
Edit: Note that Thin Installer does not run on Vista SP2 (neither does System Update.)
Here are the few simple things you have to do:
1. Download Update Retriever (UR) and Thin Installer (TI) from here.
2. Install UR on one pc and TI on all clients you want to keep updated. UR installs into the Start -- All Programs -- Thinkvantage folder, TI installs into c:\program files\thininstaller.
3. To initialize Update Retriever:
a) specify the download folder, pick a place all clients can access. Create a new folder, TI will be confused if there is other stuff in it.
b) change the settings to Severity -- Optional (assuming you want to see critical, recommended and optional downloads in the list), License -- Do not display and Status -- Active. After clicking next you enter the machine type, the op system and its language for each client you need to keep updated. Note that unless you change status to active everything will download as "test" and thus not be installed by the Thin Installer.
4. Run the download, about 1 - 1.5GB for the first type, opsys and language combination and an additional 0.5 - 1GB for each additional type depending on amount of overlap. You can be selective what you download but if you are an average home user -- just download all the items for your type/opsys/language combination(s) -- Thin Installer is a stripped down version of System Update and will decide what to install on the individual client. This is a one-time download, next time you run Update Retriever it will just download new drivers.
5. To initialize TI on each client, copy the program from the Program Files directory and paste a shortcut to the desktop. Then rightclick on the shortcut and choose Properties, and in the target field of the shortcut tab after "C:\Program Files\ThinInstaller\ThinInstaller.exe" add the following: -repository your_UR_download_directory.
6. Run the Thin installer on each client, it will perform exactly as System Update did, down to making the same mistakes that System Update did.
7. As the date is getting close when Windows Update will start distributing Vista SP2 you may want to consider using Microsoft's SPBlockerTools preventing SP2 installation for up to 12 months.
8. Debugging Tips
TI ending with message An error occurred while gathering user information is reported when running under Vista SP2 -- TI will not run in SP2.
Getting TI to "see" the database downloaded by UR is the main problem. If TI ends with a message saying corrupt or not found database you probably made a spelling mistake in the directory specified in the -repository parameter. If TI ends with a message saying no applicable packages to install it can mean a number of things:
a) If you are unused to modifying the parameters in a shortcut you may have added -repository to the second field in the shortcut tab instead of the top field labeled Target, the two fields look very similar or you just made a typo in "-repository".
b) Open UR again and first choose Modify settings on the left and double check that the directory there is the same directory you specified in -repository. Then choose Manage repository -- Update view and double check that all packages have status Active. If they don't it's not necessary to download again, just select all and hit the modify button to change status from Test to Active.
c) In C:\Program Files\ThinInstaller\logs there are update logs from TI. Open one using Notepad and in edit menu search for the string
Message: 'Share name' to use:
This will tell you in which directory TI is searching for the updates. If it can't find a -repository parameter it uses an empty default databse
d) If you used System Update regularly up to when it stopped working on April 1 and if you have an older model with not so many new driver updates it may actually happen that there are no new updates for your machine (even though you downloaded a lot.) Go to here and enter all fields except model to see what Lenovo shipped after April 1. (Don't click on driver matrices, staying on the downloads and drivers pages will give you a list in chronological order with the ones after April 1 at the top.) Also be aware that the database UR downloads from is at least 2 weeks behind when the drivers first become available on the web. Right now, the only new download in the database applicable to most notebooks after April 1 is the Access Connections 5.22 driver. To check what release you have installed open Access Connections and go to help.
I just did a clean install of a Vista64 system on my T500 and after installing the first few drivers manually (including drivers for harddisk and ethernet) let Thin Installer install the remaining 36 items for me. The only item left to fix was the known bug in the Ricoh 4 in 1 card driver SU installation. (For a clean install you need to run TI or SU more than once, it doesn't find all drivers the first time.)
Message Edited by JaneL on 05-08-2009 10:30 PM
Message Edited by zilla on 2009-05-28 12:48 PM
T500: Vista 32, 2.8GHz, 4GB RAM, 15.4" 1680x1050, 500GB 7200rpm, ATI Radeon HD3650 + Intel 4500MHD. T42: XP, 1.7GHz, 2GB RAM, 14.1" 1024x768, 250GB PATA, ATI Radeon 7500.

koolzero wrote:
When I start TI after I pointed it to my repository I get a message that no packages applicable were found. I did not download all the updates just a few to test it, will it not work unless all updates are downloaded?
Did you change status from test to active in UR before downloading? If not you can change the downloaded items in the manage repository menu.
Assuming the items you did download were not already installed on your client with TI it should work.
Message Edited by zilla on 2009-05-06 10:23 PM
T500: Vista 32, 2.8GHz, 4GB RAM, 15.4" 1680x1050, 500GB 7200rpm, ATI Radeon HD3650 + Intel 4500MHD. T42: XP, 1.7GHz, 2GB RAM, 14.1" 1024x768, 250GB PATA, ATI Radeon 7500.

Will I have to update my bios for p43 neo 3-f to use Ati 5800 series cards?

I have had this main board for a year and a half its running well I have a gpu nvidia 9800gt installed atm no problems.
just wondering if i have to update the bios because thinking on moving up to Ati 5800 series well like to know before I purchase.

No. What PSU do you have?
https://forum-en.msi.com/index.php?topic=104805.0

Hotkey package missing from Update Retriever

Hi,
I am unable to download (find) Hotkey package in Update Retriever, for deployment of x240 and t440 computers.
Is that by design or something that can be fixed?

Hi,
Welcome to Lenovo Community Forums!
I’m sorry to hear that system update in your Lenovo X240 and T440 is not able to retrieve hotkey integration features.
Ensure that you have the latest version of Lenovo system update installed. If it didn’t help, I would suggest you to manually download the drivers from Lenovo Support page by entering the MTM number of your machine in the quick path.
If you find any difficulties, please share the MTM number of your device and the operating system installed.
Best regards,
Mithun.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Update Retriever - HelloLevel_8_07_00.xml not existing in SSClientCommon folder

Hello,
Yesterday I installed a clean installation of the latest Update Retriever (updateretriever402-2011-07-27.exe) on our server and configured the latest System Update client (systemupdate401-2011-07-25.exe) to connect to it for automatic update retrieval.
This worked out fine yesterday, client connecting to the internal server and retrieving the updates.
This morning this does no longer worked, checked the tvsu_log file on the client reveals that this seems to be caused by the a file named HelloLevel_8_07_00.xml not existing in the SSClientCommon folder on the internal update retriever server.
Checking the content of the target dir on the internal server does indeed show that that file is not present, others are.
Please advice as to what the reason and solution can be.
Thanks.
*** Partial content of the clients' tvsu_log file ***
Info 2011-08-17 , 11:44:16
at Tvsu.Engine.Process.HelloProcess.Start()
Message: HelloProcess Started
Info 2011-08-17 , 11:44:16
at Tvsu.Engine.Process.HelloProcess.Start()
Message: Client level: HelloLevel_8_07_00
Info 2011-08-17 , 11:44:16
at Tvsu.Engine.Process.HelloProcess.DownloadUDF(String helloClientLevel)
Message: The UDF will be downloaded from: S:\Lenovo\TVSU_Repository\SSClientCommon/HelloLevel_8_07_00.xml
Info 2011-08-17 , 11:44:16
at Tvsu.Engine.Process.HelloProcess.DownloadUDF(String helloClientLevel)
Message: The UDF will be downloaded to-> C:\Program Files (x86)\Lenovo\System Update\session\system\SSClientCommon\HelloLevel_8_07_00.xml
Info 2011-08-17 , 11:44:16
at Tvsu.Gui.CustomComponents.Step.set_Image(StepImage value)
Message: Setting PROCESSING status.
Info 2011-08-17 , 11:44:16
at Tvsu.FileDownloader.LocalDownload.Init(FileDownloadInfo fileInfo, downloadingDelegate downDelegate)
Message: Failed to find the file from server: S:\Lenovo\TVSU_Repository\SSClientCommon/HelloLevel_8_07_00.xml
Info 2011-08-17 , 11:44:16
at Tvsu.FileDownloader.LocalDownload.Init(FileDownloadInfo fileInfo, downloadingDelegate downDelegate)
Message: some error were found in LocalDownload.Init function
Exception:
  Message: the file does not exist int the server path
  Type: System.Exception
     at Tvsu.FileDownloader.LocalDownload.Init(FileDownloadInfo fileInfo, downloadingDelegate downDelegate)
*** Content of the SSClientCommon folder on the internal update retriever server ***
26/04/2011 10:29                97 HelloLevel_8_00_00.xml
11/08/2011 15:37             1.267 HelloLevel_8_00_00L.xml
26/04/2011 10:29                97 HelloLevel_8_00_01.xml
11/08/2011 15:37             1.266 HelloLevel_8_00_02.xml
11/08/2011 15:37             1.266 HelloLevel_8_00_03.xml
11/08/2011 15:37             1.266 HelloLevel_8_00_04.xml
11/08/2011 15:37             1.266 HelloLevel_8_00_05.xml
11/08/2011 15:37             1.266 HelloLevel_8_00_06.xml
11/08/2011 15:39             1.266 HelloLevel_8_01_00.xml
11/08/2011 15:39             1.125 HelloLevel_8_02_03.xml
11/08/2011 15:39             1.125 HelloLevel_8_02_04.xml
11/08/2011 15:39             1.125 HelloLevel_8_03_01.xml
11/08/2011 15:39             1.125 HelloLevel_8_04_00.xml
11/08/2011 15:39             1.125 HelloLevel_8_04_01.xml
11/08/2011 15:39             1.126 HelloLevel_8_04_01D.xml
11/08/2011 15:39             1.126 HelloLevel_8_04_01L.xml
11/08/2011 15:39             1.125 HelloLevel_8_04_02.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_00.xml
11/08/2011 15:41             1.126 HelloLevel_8_05_00A.xml
11/08/2011 15:41             1.126 HelloLevel_8_05_00R.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_10.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_20.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_40.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_50.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_60.xml
11/08/2011 15:41             1.125 HelloLevel_8_05_70.xml
11/08/2011 15:41             1.127 HelloLevel_8_05_80.xml
11/08/2011 15:43             1.129 HelloLevel_8_05_80_314.xml
11/08/2011 15:44             1.127 HelloLevel_8_05_81.xml
11/08/2011 15:44             1.127 HelloLevel_8_05_90.xml
11/08/2011 15:42             1.127 HelloLevel_8_05_91.xml
11/08/2011 15:45             1.319 SSClientCommon_7_00_0.xml
11/08/2011 15:45             1.319 SSClientCommon_7_00_1.xml
11/08/2011 15:45             1.321 SSClientCommon_7_00_10.xml
11/08/2011 15:45             1.321 SSClientCommon_7_00_11.xml
11/08/2011 15:45             1.319 SSClientCommon_7_00_5.xml
11/08/2011 15:45             1.319 SSClientCommon_7_00_6.xml

Hi ,
Does your issue been fixed? if not, maybe you can post the full log so that I can have a look to see if I can provide some advises,thanks.

Update Retriever Update dont show anymore, they gone missing?

Hey All,
for some reason I cant see a single update in Update Retriever anymore..
What to do?

Heres the status of the the driver from XML file:
<Package id="83de32ww" name="NVIDEO4200_OPT64" description="ThinkPad Video Features [NVIDIA NVS 4200M and Quadro 1000M/2000M Optimus] for Windows 7 64">
<FileName>83de32ww_2_.xml</FileName>
<Version>8.17.12.6696/8.15.10.2321</Version>
<ReleaseDate>3/30/2011</ReleaseDate>
<Size>400125632</Size>
<URL>://download.lenovo.com/ibmdl/pub/ibmdl/pub/pc/pccbbs/mobiles/</URL>
<Mode />
<Type>Quest</Type>
<Status>Active</Status>
<PreviousStatus>None</PreviousStatus>
<LocalPath>\83de32ww\83de32ww_2_.xml</LocalPath>
<Severity>Optional</Severity>
<DisplayLicense>NotDisplay</DisplayLicense>
- <SystemCompatibility>
<System mtm="4236" os="Windows 7" oslang="EN" />
<<System mtm="4239" os="Windows 7" oslang="EN" />
AAnd here is the command to install the drives via Thininstall:
ThinInstaller.exe /CM -search A -action INSTALL -noicon -includerebootpackages 1,2,3,4 -repository C:\lenovo_updates

Update Retriever - Missing Intel Management Engine Interface Driver for Lenovo Twist (334725RU)

I am left with two unknown devices in Device Manager. It appears to be the Intel Management Engine Interface Driver, which is unavailable in Update Retriever. I see it on the website as gars04ww.exe.
Please add this to the repository.
Thanks,
Hans
Hans Lima

The other one is the Realtec Card Reader gaxm05ww.exe
Hans Lima

Fault in Update Retriever bios's

Similar Messages

Maybe you are looking for