No Windows Imaging Components after crash

Running Win7 64 bit

I had a system crash 5 days ago. I was tinkering with virtualization
software called 'Virtualbox'. The crash rendered the OS unbootable
until I let windows try to repair itself. Far as I understood the
dialogs the repair facility replaced system files and rolled back to
the last bootable state.

I didn't really notice any problems other than quite a few updates to
install (12). I installed all of them and finally windows update
reports 'no updates available'.

Yesterday when I tried to run a Garmin (The gps folks) application
called `Basecamp' and got an error about Windows Imaging Components
missing or similar (I wish I'd kept the error verbatim but did not).
And 'basecamp' would not start.

Rather than researching I just dashed off and tried re-installing
basecamp. But first I uninstalled the version on the OS.

I was not able to re-install 'Basecamp' and the attempt received this
error: MSI: error 'InstallerAlreadyRunning'

After googling awhile I find info that suggests I need to re-install
Windows Imaging Components but when I try to install the latest one
for 64 bit, that fails with this error:

'Setup could not find the update.inf
file needed to update your system'

I'm hoping someone here has seen a similar problem and might have some
suggestions about how to proceed.

Harry Putnam wrote:
Running Win7 64 bit

I had a system crash 5 days ago. I was tinkering with virtualization
software called 'Virtualbox'. The crash rendered the OS unbootable
until I let windows try to repair itself. Far as I understood the
dialogs the repair facility replaced system files and rolled back to
the last bootable state.

I didn't really notice any problems other than quite a few updates to
install (12). I installed all of them and finally windows update
reports 'no updates available'.

Yesterday when I tried to run a Garmin (The gps folks) application
called `Basecamp' and got an error about Windows Imaging Components
missing or similar (I wish I'd kept the error verbatim but did not).
And 'basecamp' would not start.

Rather than researching I just dashed off and tried re-installing
basecamp. But first I uninstalled the version on the OS.

I was not able to re-install 'Basecamp' and the attempt received this
error: MSI: error 'InstallerAlreadyRunning'

After googling awhile I find info that suggests I need to re-install
Windows Imaging Components but when I try to install the latest one
for 64 bit, that fails with this error:

'Setup could not find the update.inf
file needed to update your system'

I'm hoping someone here has seen a similar problem and might have some
suggestions about how to proceed.


Have you run Windows system file-checker in a Command Prompt window?
sfc /scannow

Ed

Ed Cryer writes:

Harry Putnam wrote:
Running Win7 64 bit


[...]

I was not able to re-install 'Basecamp' and the attempt received this
error: MSI: error 'InstallerAlreadyRunning'

After googling awhile I find info that suggests I need to re-install
Windows Imaging Components but when I try to install the latest one
for 64 bit, that fails with this error:

'Setup could not find the update.inf
file needed to update your system'

I'm hoping someone here has seen a similar problem and might have some
suggestions about how to proceed.


Have you run Windows system file-checker in a Command Prompt window?
sfc /scannow

Its actually running now... I had to schedule the check for next
bootup. Its a very lengthy and thorough chk apparently. Takes a half
hour or more to complete 5 stages. Its on the 5th stage now. But
nothing bad reported so far.

OK, that finished while I was writing this... no problems reported.

When you suggested that, what were you thinking it would show? What
else might I do to get straightened out here?

Harry Putnam wrote:
Ed Cryer writes:

Harry Putnam wrote:
Running Win7 64 bit


[...]

I was not able to re-install 'Basecamp' and the attempt received this
error: MSI: error 'InstallerAlreadyRunning'

After googling awhile I find info that suggests I need to re-install
Windows Imaging Components but when I try to install the latest one
for 64 bit, that fails with this error:

'Setup could not find the update.inf
file needed to update your system'

I'm hoping someone here has seen a similar problem and might have some
suggestions about how to proceed.


Have you run Windows system file-checker in a Command Prompt window?
sfc /scannow

Its actually running now... I had to schedule the check for next
bootup. Its a very lengthy and thorough chk apparently. Takes a half
hour or more to complete 5 stages. Its on the 5th stage now. But
nothing bad reported so far.

OK, that finished while I was writing this... no problems reported.

When you suggested that, what were you thinking it would show? What
else might I do to get straightened out here?


That sounds like a drive error check, not a Win7 system check.
Open All Programs/ Accessories/ right click Command Prompt & select Run
As Administrator.
Type in "sfc/ scannow" without the quotes.

Ed

Ed Cryer writes:

When you suggested that, what were you thinking it would show? What
else might I do to get straightened out here?



That sounds like a drive error check, not a Win7 system check.
Open All Programs/ Accessories/ right click Command Prompt & select
Run As Administrator.
Type in "sfc/ scannow" without the quotes.

No, its a scan and 4 more checks including bad sectors so it cannot be
done with the system running.

But to satisfy your suggestion I ran just the 'sfc /scannow' again
from a dos box, and not surprisingly got the same results. (no output
indicating any problems)

I asked you this last time but maybe now you will be willing to say
why you are suggesting a disk scan?

In my OP, I said I was hoping someone would reply who had seen a
similar problem concerning Windows Imaging Components.

Did you solve a Windows Imaging Component problem with a disk scan or
is there some other reason I should be running that?

Do you have any other ideas about how to solve the problem I described?

Ken1943 writes:

I would run chkdsk /r from a command prompt. The file indexing (forget
the real name for it) on the disk could have gotten corrupted. Do this
after you reboot in case something is running.

Yeah, I did that. So do you think what I'm seeing is NOT related to
Windows Imaging Components or did you mean that maybe running chkdsk
/r would unearth the update.inf file?

Ken1943 wrote:
On Sat, 17 Aug 2013 16:58:05 -0400, Harry Putnam
wrote:

Ken1943 writes:

I would run chkdsk /r from a command prompt. The file indexing (forget
the real name for it) on the disk could have gotten corrupted. Do this
after you reboot in case something is running.
Yeah, I did that. So do you think what I'm seeing is NOT related to
Windows Imaging Components or did you mean that maybe running chkdsk
/r would unearth the update.inf file?

Sounds like Virtualbox screwed up your system. You may have to do a
repair reinstall of Windows 7. Did it once and it's not as easy as XP
was.

If this is a branded computer, you may have to go to the manufacturer web
site and ask there. Hope you don't have to use system restore.


KenW

I would be looking at

sfc /scannow

and CheckSUR, before falling back to a Repair Install. The SFC
will attempt to ensure executable files are in place
where they should be. And CheckSUR (System Update
Readiness), has something to do with Windows Update.
There is also a separate "FIXIT" file from Microsoft,
which can reset Windows Update state info.

http://support.microsoft.com/kb/947821

Virtual machine software installation, adds drivers to
the OS. So it's not a "pure application" as such. It
hooks things and is not completely innocuous. For example,
it could screw up networking, given half a chance. Uninstalling
VirtualBox, should remove those drivers (in theory).

I don't understand what the VirtualBox crash would do,
except perhaps to damage the myriad registry settings
put there by WIC. Maybe the registry, or some hive in
the registry, got damaged. Using System Restore, to a
point before the failure, should put back a good
copy of the registry (at the expense of undoing
lots of other changes made along the way).

In my experience with VirtualBox and VPC2007, it's
usually the *internal* environment (guest OS problems)
rather than host side problems. One of the host side
problems I've seen, of all things, is changing the
timing on the floppy drive read/write, and causing
it to blow the interleave factor (makes the floppy
really slow to use).

Paul