Given that it works in one location, and not in another, including what those locations are in a problem report would be (a) helpful, and (b) (I would have hoped) obvious :-) Best guess is the original location is somewhere that Windows (now) regards as "protected" in some measure (e.g. "`C:\Program Files`") and the recent update has imposed stricter permissions on that area (or, perhaps, has removed looser permissions you might have given it in the past). Also, it should be noted that SQLiteBrowser is a 3rd-party product. If your investigations into "protected locations" doesn't lead anywhere, try accessing the database using the SQLite CLI command-line program to eliminate anything SQLiteBrowser might be doing.