I think the errors you pasted from the log are not the root cause. The real
error (and cause for rollback) is probably somewhere earlier in the log and
those errors you pasted came from unsuccesfull rollback. Try doing a clean
install - you may need to get empty hdd or shrink existing partition
(gparted live cd should help). Also get Beta Client and submit the entire
logs.
Here is my detailing on how to find the right logs since I am not sure
whether you found all the appropriate logs or not:
---
Finding setup logs, reporting and attaching logs to report, figuring out
what device or driver causes hangs or crash during setup:
1. google -> beta client (
http://go.microsoft.com/fwlink/?LinkId=43655)
The first link should be Microsoft link. It needs .NET but I think it will
be installed if you try to run it without it..
2. finding and identifying the correct logs
setupapi.app.log
setupapi.dev.log <<-- last 100 lines here may indicate the hanging driver
These are the primary setup logs, there are others but these are the major.
Hint: Before searching logs try Folder Options and enable viewing of hidden
folders and files. Also try Run diskmgmt.msc -> assign drive letters for
partitions with no drive letters.
A:
There can be multiple logs with the same name, but they are different! First
look at the drive you tried to install Vista to, if it has Vista
Windows\INF\ directory and the mentioned logs files.
B: early setup failure
If you can't find Windows VISTA directory (if setup did not get so far) then
look all volumes/partitions in the drives that were on the machine during
the install for directories starting with $. There are 2-4 of them (possibly
in different partitions) depending on when the setup failed. Search for .log
under all the *:\$WINDOWS.. and again look at the date/minute timestamp to
see which of the logs was changed just before the failure occured.
Also see that the date and Minute timestamp of the log files are around the
time when the setup failed, sometimes a setup/install failure causes the
computer to automatically reboot and the setup will run again but failing in
different way than the first time (making the bug report less useful). For
best bug report it's better to catch the failure when it first happens. Yes
it means starting the install all over again and keeping eye on it. But this
will guarantee that the last line in the log will be around the time of the
failure. If it is a driver crash then you can figure out the offending
driver yourself just by looking at the last twenty or so lines of
setupapi.dev.log.
JMartin said:
I am thinking it has to do with the chipset. Does anyone else know if there
is an issue with the intel 875P chipset? It could also be the damn dell
bios,
or the intel smbios, but I cant be sure. I have tried to search to see
what
chipsets are compatable, but I cant find a white paper anywhere on the
supported hardware. The HC program really doesnt tell me much either.
droid said:
Generally the driver and hardware related errors are found in
setupapi.dev.log, but in this case maybe the setup did not get that far
as
to make that file. If the error happens in setupapi.app.log log *only*
(not
dev.log) and is such as yours, it's possibly a setup bug and you should
report it and attach the log files. Google for Beta Client.. The first
link
should be a Microsoft link.
JMartin said:
Ok, i got what I think is an error log(s)
Here is what they say:
Error [0x050041] DU Search failed with the OperationResultCode
=
3
Error [0x050098] DU Error while setup update search/download
[gle=0x000003f0]
Error [0x050041] DU Search failed with the OperationResultCode
=
3
Error [0x050098] DU Error while setup update search/download
[gle=0x000003f0]
Error [0x050041] DU Search failed with the OperationResultCode
=
3
Error [0x050098] DU Error while setup update search/download
[gle=0x000003f0]
That log was in windows~.bt\sources\panther
this is a roll back error log:
Error [0x064189] IBSLIB RollbackExecuteSequence: threw exception.:
class RollbackException: RollbackException: Error(2), Rollback failed.
void __thiscall CIBSCheckpoint::Rollback(const unsigned short *)
[gle=0x00000002]
Error [0x0e00cd] TOOL OS Rollback: ExecuteRollback
failed.[gle=0x00000002]
Error [0x0e00da] TOOL ReportSQMRollback: SqmStartUpload failed.
any suggestions?
:
Hi everyone. I am having a major issue installing vista. I have a dell
demension 8300 with a 3ghz P4 (w/HT), 80Gb HD, intel 875p chipset, 1.2
Gb
of
ram, and an ATI radeon 256MB AGP video card.
I downloaded the image and burned it to two seperate disks. I had no
errors
on the burn and it checksum'd ok. I tried to upgrade from xp home, and
after
a few reboots it says windows vista failed to upgrade. It then rolls
back
and
XP starts normally. I have wiped my drives and made 2 partitions. I
reinstalled xp on one and tried to install vista on the other by
running
the
setup from xp. that went through and rebooted a few times and then
said
vista
failed to install. I tried to boot from the dvd and it gets to the
vista
splash screen and then idles until it restarts and "rolls back".
The error message says check the setup log for more details, but I
cannot
find the "setup log" and I have a feeling that it erases it when the
system
"rolls back".
I have ordered the dvd from microsoft, and I am currently awaiting its
arrival. maybe that will work better. Does anyone know of anything I
can
do
in the mean time to try to get the install to work?
The hardware compatability program said that my system is capable of
running
"core vista experiences" but it did say that the simbios was not
compatable,
but upon getting the latest drivers from intel, the bios is now
compatable. I
dont know what else to try. does anyone have any ideas?
Thanks,
Jim Martin
