Jump to content
LaunchBox Community Forums

Launchbox Folder constantly returning to 'Read-Only'


shadowblind
Go to solution Solved by shadowblind,

Recommended Posts

Hi! Nearly every time I launch Bigbox and go through the various platforms like normal, I try and return to the Platforms view and eventually (within 5 or so minutes of usage) come across an error message. Turns out, the Launchbox folder is constantly reverting to 'Read Only' no matter how often I uncheck that setting or change the security settings so that anyone can read/write to it. Any thoughts on what's causing this? It renders Bigbox unusable to any period of time greater than roughly 5 minutes.

Link to comment
Share on other sites

Not sure if this helps, but this is the log I'm getting:

 

"Object reference not set to an instance of an object.

App:     Big Box
Version: 13.15
Theme:   CoverBox
Type:    System.NullReferenceException
Site:    Void InvokeProperty(System.String)
Source:  BigBox

   at Unbroken.LaunchBox.Windows.BigBox.ViewModels.FiltersViewModelBase.InvokeProperty(String value)
   at RegistryPolicy.ManageBridge(Object , String value, RegistryPolicy )
   at Unbroken.LaunchBox.Windows.BigBox.ViewModels.FiltersViewModelBase.RefreshGameImages()
   at RulesProducer.ManageBridge(Object , RulesProducer )
   at Unbroken.LaunchBox.Windows.BigBox.NavigationManager.Back()
   at ServicePublisher.ManageBridge(Object , ServicePublisher )
   at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.Back()
   at AttributePolicy.ManageBridge(Object , AttributePolicy )
   at Unbroken.LaunchBox.Windows.BigBox.ViewModels.CoverFlowWithDetailsGamesViewModel.OnEscape(Boolean held)
   at Unbroken.LaunchBox.Windows.BigBox.NavigationManager.OnEscape(Boolean held)
   at ParamPublisher.ManageBridge(Object , Boolean held, ParamPublisher )
   at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.OnEscape()
   at ImporterPublisher.ManageBridge(Object , ImporterPublisher )
   at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.HandleKeyDown(KeyEventArgs e)
   at InstanceInstance.ManageBridge(Object , KeyEventArgs e, InstanceInstance )
   at Unbroken.LaunchBox.Windows.BigBox.Views.MainView.DefineParameter(Object param, KeyEventArgs result)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   at System.Windows.Interop.HwndKeyboardInputProvider.ProcessKeyAction(MSG& msg, Boolean& handled)
   at System.Windows.Interop.HwndSource.CriticalTranslateAccelerator(MSG& msg, ModifierKeys modifiers)
   at System.Windows.Interop.HwndSource.OnPreprocessMessage(Object param)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Recent Log:

   6:32:19 PM Exception"

Link to comment
Share on other sites

We don't ever set that flag on a directory so isn't our app doing so. That being said I'm wondering if this isn't an issue with the symlink creation we do at the start. What file format is your drive formatted in? If you right click the drive in File Explorer and press properties on the window that opens there is a label called "File System". Does it say NTFS or something else?

Link to comment
Share on other sites

8 hours ago, C-Beats said:

We don't ever set that flag on a directory so isn't our app doing so. That being said I'm wondering if this isn't an issue with the symlink creation we do at the start. What file format is your drive formatted in? If you right click the drive in File Explorer and press properties on the window that opens there is a label called "File System". Does it say NTFS or something else?

Looks like the drive is NTFS...hope that helps!

Link to comment
Share on other sites

15 hours ago, shadowblind said:

Looks like the drive is NTFS...hope that helps!

Would have been more helpful that it wasn't since the solution around it is known. Now that all the easy to solve potential causes have been eliminated it'll be a bit more difficult to sniff out why your system seems to be acting so wildly different to others.

Are you running any sort of syncing application that may be touching your file system? I've noticed you seem to be having a lot of disk read errors across several threads and those can sometimes lock resources we are trying to read and cause issues.

  • Like 1
Link to comment
Share on other sites

  • Solution
9 hours ago, C-Beats said:

Would have been more helpful that it wasn't since the solution around it is known. Now that all the easy to solve potential causes have been eliminated it'll be a bit more difficult to sniff out why your system seems to be acting so wildly different to others.

Are you running any sort of syncing application that may be touching your file system? I've noticed you seem to be having a lot of disk read errors across several threads and those can sometimes lock resources we are trying to read and cause issues.

Nice call! Found out what was causing the problem by your advice: A program called Linux File System for Windows (by Paragon Software). Used it to transfer files to/from Linux USB drives. Don't use it anymore but it was running in the background. Removing it seems to have totally eliminated the issue. So, the issue WAS with syncing software.

Thanks for your help, really appreciate it!

  • Game On 1
Link to comment
Share on other sites

13 hours ago, shadowblind said:

Nice call! Found out what was causing the problem by your advice: A program called Linux File System for Windows (by Paragon Software). Used it to transfer files to/from Linux USB drives. Don't use it anymore but it was running in the background. Removing it seems to have totally eliminated the issue. So, the issue WAS with syncing software.

Thanks for your help, really appreciate it!

Awesome glad you were able to get it sorted. Hopefully it helps eliminates other issues I've seen you asking about on the forums as well and you can begin to enjoy your time with the software.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...