Internal Error 2330. 1392 when uninstalling/repairing MS Money 200

Hello,

I installed MS Money 04 a few weeks ago and all was fine. Now, all is
corrupt. Trying to uninstall, repair, or install again from the CD all
result in the above error, "directory is not empty".

Further, when I go to delete the C:\Program Files\Microsoft Money folder,
I get the error:
Error 0x80070091: The directory is not empty.

Just trying to open the Money folder yields:
The file or directory is corrupted and unreadable.

I've tried turning off UAC, turning off McAfee, and running in Safe Mode,
but I still can't uninstall or delete the folder.

Any thoughts?

Windows Vista Home Premium
Dell XPS M1210

I dunno the exact answer, but in this situation the next thing I'd try is
CHKDSK, to look for any coruption in the file system.

At a command prompt (run as administrator), do:

C:\>chkdsk c: /f /v

and then reboot the machine. A chkdsk of the system drive can only run while
the system is booting.

Let us now how you get on.

Andrew

Hello again,

Your suggestion "sort of" worked, but dug up another problem. I was not
able to run chkdsk the way you suggested. When I restarted, the chkdsk
simply did not run. After some online research, it seems the autochk.exe is
probably corrupt.

I was able to get chkdsk to run by tapping F8 for the alternate startup
modes, selecting repair computer, then running the first choice, "fix startup
problems" or something like that. That ran chkdsk for about 15 minutes.
Afterward, all my MS Money problems were solved.

However, autochk is still corrupt. How do I fix that?

Brian

"Andrew McLaren" wrote:

> I dunno the exact answer, but in this situation the next thing I'd try is
> CHKDSK, to look for any coruption in the file system.
>
> At a command prompt (run as administrator), do:
>
> C:\>chkdsk c: /f /v

"briantrease" <> wrote ...
> I was able to get chkdsk to run by tapping F8 for the alternate startup
> modes, selecting repair computer, then running the first choice, "fix
> startup
> problems" or something like that. That ran chkdsk for about 15 minutes.

Hi Brian,

15 minutes? Yowza! That sounds like it was doing a lot of work, in other
words, it had to fix many things. For comparison, on my Core 2 Duo 2.2GHx
machine, chkdsk /f of a 320 GB drive tales about 90-120 seconds. Anyway
chkdsk has run on your drive now, that's good.

> Afterward, all my MS Money problems were solved.

Cool. That tends to support the theory the install/uninstal problem was
caused by some corruption in the file system.

> However, autochk is still corrupt. How do I fix that?

Hmm, well, I don't recognise that as a "well-known" problem in Vista.
Although there has been a small but steady stream of problems location
autochk.exe, over the years. I suspect some 3rd party disk utility is
messing with the file (eg some defrag app, backup app, or the like). Also,
if you are dual booting between XP and Vista, that could cause some file
system weirdness, unless done exactly right.

To repair a damaged autochk.exe, the first thing I'd try is SFC ("System
File Checker"). This is a built-in facility of Vista.

Open a command prompt as administrator.

Run the command "sfc /verifyonly". This only reports, it does not change
anything. Note any errors it returns.

Next, run "sfc /scannow". This will check all protected Operating System
files and replace any which it detects are damaged. It may prompt you to
insert the Vista installation DVD.

I would definitely try to let sfc repair the file first, before trying to
manually replace it with a fresh copy of autochk, extracted from the Vista
Install.wim file. That is a possibility, but is fraught with peril and
difficulty.

You should probably run Chkdsk on a regular basis, until you work out what
is messing up your file system.

Hope it helps
Andrew

Hello again, and sorry for the long delay,

I've tried sfc /verifyonly and sfc /scannow, but the problem remains. I get
the following data from the CBS.log, indicating that autochk and 2 other
files are bad (tcpmon.ini and settings.ini). Also, I've found a similar post
with another user experiencing the same problems. The recommendation over
there is to run a Vista Upgrade, but I'm not sure if this is overkill.

http://windowshelp.microsoft.com/com...=en-us&m=1&p=1
The above post refers to this article
http://vistasupport.mvps.org/repair_..._vista_dvd.htm

Any suggestions? Should I try the Install.wim option, or some of the
suggestions from the other post?

Thanks in advance!!
Brian

2007-07-17 18:40:35, Info CSI 0000001c Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6000.16386_none_dfbd2 b4dc4d6121b\autochk.exe
do not match actual file [l:22{11}]"autochk.exe" :
Found: {l:32 b:tZN+W/XkksJHvDvnrLN0OmikXDWw+uH0l1SsXGI9vdg=} Expected:
{l:32 b:wSKkBQ/YXr4909/sTSrtOCsbCRFN0hw8v/ecE99qI6V=}
2007-07-17 18:40:35, Info CSI 0000001d [SR] Cannot
repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk,
Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2007-07-17 18:40:36, Info CSI 0000001e Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6000.16386_none_dfbd2 b4dc4d6121b\autochk.exe
do not match actual file [l:22{11}]"autochk.exe" :
Found: {l:32 b:tZN+W/XkksJHvDvnrLN0OmikXDWw+uH0l1SsXGI9vdg=} Expected:
{l:32 b:wSKkBQ/YXr4909/sTSrtOCsbCRFN0hw8v/ecE99qI6V=}
2007-07-17 18:40:36, Info CSI 0000001f [SR] Cannot
repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk,
Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2007-07-17 18:40:37, Info CSI 00000020 Repair results
created:


2007-07-17 18:49:30, Info CSI 000000df Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04 210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
{l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2007-07-17 18:49:30, Info CSI 000000e0 [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2007-07-17 18:49:34, Info CSI 000000e1 Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04 210aeaa5e863a\tcpmon.ini
do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=} Expected:
{l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
2007-07-17 18:49:34, Info CSI 000000e2 [SR] Cannot
repair member file [l:20{10}]"tcpmon.ini" of
Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch


2007-07-17 18:50:58, Info CSI 000000fc Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6000.16386_none_cca5e 9c129bd0a02\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:zROVK9Mfp77kOMRFbV0UIrKe21a++Wg54PRgEPEEsMg=} Expected:
{l:32 b:40ijQez8dnId2/xBxTWnf/gsCddJvRLR5cH9MDStaEu=}
2007-07-17 18:50:58, Info CSI 000000fd [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2007-07-17 18:50:58, Info CSI 000000fe Hashes for file
member
\SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6000.16386_none_cca5e 9c129bd0a02\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:zROVK9Mfp77kOMRFbV0UIrKe21a++Wg54PRgEPEEsMg=} Expected:
{l:32 b:40ijQez8dnId2/xBxTWnf/gsCddJvRLR5cH9MDStaEu=}
2007-07-17 18:50:58, Info CSI 000000ff [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2007-07-17 18:51:01, Info CSI 00000100 Repair results
created:


"Andrew McLaren" wrote:

> "briantrease" <> wrote ...
> > I was able to get chkdsk to run by tapping F8 for the alternate startup
> > modes, selecting repair computer, then running the first choice, "fix
> > startup
> > problems" or something like that. That ran chkdsk for about 15 minutes.
>
> Hi Brian,
>
> 15 minutes? Yowza! That sounds like it was doing a lot of work, in other
> words, it had to fix many things. For comparison, on my Core 2 Duo 2.2GHx
> machine, chkdsk /f of a 320 GB drive tales about 90-120 seconds. Anyway
> chkdsk has run on your drive now, that's good.
>
> > Afterward, all my MS Money problems were solved.
>
> Cool. That tends to support the theory the install/uninstal problem was
> caused by some corruption in the file system.
>
> > However, autochk is still corrupt. How do I fix that?
>
> Hmm, well, I don't recognise that as a "well-known" problem in Vista.
> Although there has been a small but steady stream of problems location
> autochk.exe, over the years. I suspect some 3rd party disk utility is
> messing with the file (eg some defrag app, backup app, or the like). Also,
> if you are dual booting between XP and Vista, that could cause some file
> system weirdness, unless done exactly right.
>
> To repair a damaged autochk.exe, the first thing I'd try is SFC ("System
> File Checker"). This is a built-in facility of Vista.
>
> Open a command prompt as administrator.
>
> Run the command "sfc /verifyonly". This only reports, it does not change
> anything. Note any errors it returns.
>
> Next, run "sfc /scannow". This will check all protected Operating System
> files and replace any which it detects are damaged. It may prompt you to
> insert the Vista installation DVD.
>
> I would definitely try to let sfc repair the file first, before trying to
> manually replace it with a fresh copy of autochk, extracted from the Vista
> Install.wim file. That is a possibility, but is fraught with peril and
> difficulty.
>
> You should probably run Chkdsk on a regular basis, until you work out what
> is messing up your file system.
>
> Hope it helps
> Andrew
>
>