PendingFileRenameOperations key with non-existent files listed

[Gregg Hill]

Hello!

While installing some software to log and monitor a WatchGuard firewall, I
kept getting a message about an installation that had not completed. Google
searches said to check for the presence of the "PendingFileRenameOperations"
under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager].
It is there, and it (currently) points to the following non-existent files.
The proposed fix is to delete the key and reboot, which I have done multiple
times. A reboot without deleting the key also works, but this key keeps
repopulating itself. The actual file name always differs, and the folder is
always empty.

\??\C:\WINDOWS\system32\FxsTmp\fxs6C.tmp

\??\C:\WINDOWS\system32\FxsTmp\fxs39B.tmp

\??\C:\WINDOWS\system32\FxsTmp\fxs3EC.tmp

I can finish an installation of software (WatchGuard System Manager) and
verify that the key is gone, then reboot, verify the key is gone, then look
at it the next morning, and the key is back.

Why does this key keep reappearing?

Gregg Hill

--

Apostrophes: when in doubt, leave them out! You will be correct more often
than not.

Its = Belonging to it. For example, "Look at the sky. Its color is blue."
It's = It is. For example, "It's hot today."
It's = It has. For example, "It's been nice talking to you."
Its' = completely incorrect usage. Stop it!

[Cliff Galiher]

It is a known bug in WSM 10.x. It just doesn't clean up after itself. It
may also be in previous versions of WSM, of that I'm not sure. I noticed it
when I moved from WFS to Fireware pro, so I had to jump a couple of versions
of WSM (8 and 9 specifically) so that was when I noticed it. Watchguard has
confirmed this as a bug to me, but no mention of a fix.

Truthfully, on an unrelated note, somewhere along that same time, Watchguard
switched from flat text file logging to using a PostgreSQL database. And
although you'd *think* SQL access would be faster, their log viewer is
ungodly painful and slow. For me, WSM 10.x is a *complete* loser. Due to
that, and other reasons (I don't like their yearly subscription model for
even basic bug fixes) I've moved away from Watchguard and now install Cisco
ASA boxes (for that pricepoint anyways.) I've been much happier.

-Cliff

"Gregg Hill" <greggmhill at please do not spam me at yahoo dot com> wrote in
message news:eOGZfVOd...@TK2MSFTNGP03.phx.gbl...

[Gregg Hill]

Cliff,

I see the same folder on an SBS 2003 system that has never had any WG
software installed. Judging from its name, it sound like something to do
with the fax service.

Are you saying that the temp files in that folder that start with "fxs" are
from WatchGuard?

I am new to WG, but I have seen a LOT of complaints regarding the new
logging format.

Gregg Hill

"Cliff Galiher" <cgal...@gmail.com> wrote in message
news:A4F89CBE-5924-43E1...@microsoft.com...

[Cliff Galiher]

To be honest, I couldn't tell you the details of the bug. All I know for
sure is that it seems to be a problem with the way that particular instance
of installshield interacts with the system. I don't know if they are using
a custom action in the MSI or if they are using a retired API, but when I
dug into it (it has been over a year now) I finally got Watchguard to admit
that they have problems on certain Windows server setups. *shrug* Sorry,
wish I could give you more.

-Cliff

"Gregg Hill" <greggmhill at please do not spam me at yahoo dot com> wrote in

message news:eHlu5kQd...@TK2MSFTNGP04.phx.gbl...