FBWF and shortcut creation

  • Thread starter Thread starter ArtRab
  • Start date Start date
A

ArtRab

We have an FBWF image with two exclusion areas relating to our app. Nothing
else is excluded.

If FBWF is enabled and I create a shortcut to an item in some system area
(e.g. explorer.exe) which is protected and move the shortcut to the desktop,
I find that the shortcut is persisted across a reboot. I would expect the
shortcut to not exist after a reboot with FBWF enabled. If I move a shortcut
position and reboot the shortcut comes back to it's original position which
is what I expected.

All other indications are that FBWF is working correctly so how come you can
create a shortcut on the desktop when enabled and it's persisted to the next
reboot.

Thanks,

Art
 
In order to get a clearer idea, we need to know a bit more information.
Please let us know
1) what are in the exlusion list? Did you power-cycled or restarted?
2) how have you verified FBWF is working otherwise? Have you created a file
and checked if the file is still present after power/recylce?
 
The exclusion areas are \program files\Cineform and \Program Files\Silicon
Imaging. Also \regdata is shown in the exclusion list when I type fbwfmgr
even though I didn't explicitly exclude it.

I did both a power cycle and a graceful reboot - no difference. on creating
shortcuts

I copied a file from the exclusion area into C: and rebooted. The file was
not in C: after a reboot. I deleted another file from C: - it was still there
after a reboot.When I type fbwfmgr, it comes back as enabled. I move
shortcuts on the desktop to a different desktop position. After a power
cycle/reboot, the shortcuts return to their originsl positions. All
indications are that FBWF is working. correctly.
 
I hope that you have done /addvolume after enabling fbwf. Your description
clearly shows that the FBWF works. Please share the result of fbwfmgr
/displayconfig command.
 
Back
Top