Home/Support/Support Forum/Problems with System State Backup because of Anywhere USB
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Problems with System State Backup because of Anywhere USB

0 votes
We are experiencing systemstate backup-problems of a windows 2008 x64-server with anywhere usb-drivers (V2.70 installed in 2010, updated to V3.51 in the meantime.)
Reviewing the logs it looks like:
Additionally we get snapshot-warnings (file not found) for the followking files:
c:\documents and settings\all users\start menu\programs\anywhereusb\anywhereusb release notes.lnk

It seems the uninstall did not really cleanup after itself/all references in the system.

Please advise / give instructions on how to manually remove all traces of the old/removed files so SystemStateBackup does not fail anymore.

Many thanks in advance for all efforts!

asked Feb 24, 2016 in USB Serial by mkruege New to the Community (1 point)

Please log in or register to answer this question.

1 Answer

0 votes
Best answer
It sounds like (unfortunately), you may be running into an old AnywhereUSB installation-related bug, per this KB article:

answered Feb 24, 2016 by jeremym Veteran of the Digi Community (1,687 points)
selected Feb 25, 2016 by mkruege
Thank you very much for your help!
Unfortunately the (digi-)answer to my problem is hard to accept...
That is certainly understandable.

If you haven't already, you can try to manually deleting most of those files from the hard drive.

The .inf files may need to be uninstalled through the "pnputil" utility.  If you issue the command "pnputil -e > pnputil.txt" that should create a new text file called pnputil.txt (you can actually name it whatever you want) and list all of the currently installed .inf files.  Then you could go through them and confirm that the stale ones are 11, 12, and 13.  Might want to search for "digi" or "anywhereusb" too.  Any .inf files you want to uninstall should be done by "pnputil -u" for example "pnputil -u oemxx.inf" if I recall correctly.

No promises here but this could be worth trying.