New
#1
7000 to 7048 upgrade, no go
I'm trying to upgrade from 7000 to 7048.
But i only get " setup was canceled", "setup can't continue. Restart the computer and restart setup""
where can I find the logfiles and see what error it is?
I'm trying to upgrade from 7000 to 7048.
But i only get " setup was canceled", "setup can't continue. Restart the computer and restart setup""
where can I find the logfiles and see what error it is?
Hi xtrem and welcome,
Are you trying to upgrade from a 32 bit to a 64 bit build or vice versa? If so, you can only upgrade from a 32 bit to a 32 bit or 64 to a 64, not 32 bit to 64 bit. You'd have to do a clean install for that.
But have you actually restarted and ran Setup again like it says? Sounds weird but you have to run setup, then it tells you to restart and run setup again. Do that and it should install.
Upgrading from 7000 x64 to 7048 x64.
Yes I have tried with 3 different torrents and restarted, etc. Same error everytime
Sorry xtrem, I don't know why it would be giving you an error, unless maybe your ISO/Setup files for 7048 were damaged or incomplete in some way. You could look in your Event Viewer and see if you get any specific error code...
Upgraded 7000 x64 to 7048 x64 too. The upgrade went fine without errors, but since I'm having random explorer crash and sometimes windows services that randomly shutdown/crash.
Not even mentioning that I had to reinstall or repair install many softwares after upgrading and it took me as long as if I had done a fresh install... not sure if others who upgraded from 7000 to 7048 have had similar problems, but it's probably best if you do a fresh install.
Have you disabled (including the self-protect options depending of your antivirus/malware protection) or uninstalled your antivirus and other security software before starting the upgrade?
I have tried with 3 different ISOs.
where should I check for error? aren't any setup log files?
Try to your install your build 7048 in a virtual machine to see if it's really your iso/files that are messed up instead of wasting your bandwidth downloading isos. If W7 doesn't install in the VM, then it's the iso(s). Otherwise, it's either a security software that blocks the install, the iso wasn't burned well, or burnt at full speed on a tired/too scratched DVD-/+rw disk. If you installed it from the hard drive, then something might have been corrupted when you extracted the files from the iso. It could be many things.
If your iso install fine in a Virtual machine like VMWare, start looking at what's installed on your computer and what could possibly cause an upgrade failure.
trying different iso doesn't do anything if the problem is caused by a third party software. Antivirus/anti-malware/firewall software have security that prevent their files from being removed, altered or deleted and it may cause problem during a system upgrade. Have you tried to upgrade after removing such software as I mentioned in the post above yours?
Last edited by Chris34; 11 Mar 2009 at 09:16. Reason: My bad English
Try %systemroot%/Panther,
or C:\$WINDOWS.~BT\Sources\Panther\
There are a hefty LOT of log files there.
If you've got vmware then you can try and instal your Virtual machine into a real one (use the V2P - Virtual to Physical conversion utility) or restore an acronis backup image into a real partition with Acronis Universalrestore -- it will try and find the physical windows drivers from the windows install.
It won't ne a pefect 100% match but it should at least boot and you can manually update any missing drivers.
Works a treat --saves a lot of work too as installing on a VM in the first place is painless.
Cheers
jimbo
arkhi: yes, about 300MB log file :)
now I tried my iso in a VM. No problem upgrading from 7000 x64 to 7048 x64.
I will try to remove as much hardware and anti-virus until I found whats i giving me errors
edit: finally the logfile opened.
2009-03-11 13:49:12, FatalError [0x090001] PANTHR Exception (code 0xE06D7363: <unknown>) occurred at 0x000007FEFDA3AB7D in C:\Windows\system32\KERNELBASE.dll (+000000000000AB7D).
last entry in setuperr.log. anyone knows why it occurs