Jump to content

System.IO.IOException when opening PkHex


sup3p

Recommended Posts

Exception Details:
System.IO.IOException: The filename, directory name, or volume label syntax is incorrect.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileSystemEnumerableIterator`1.AddSearchableDirsToStack(SearchData localSearchData)
   at System.IO.FileSystemEnumerableIterator`1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)
   at PKHeX.Core.SaveUtil.GetSavesFromFolder(String folderPath, Boolean deep, IEnumerable`1& result)
   at PKHeX.Core.SaveFinder.GetSaveFilePathsFromFolders(IEnumerable`1 foldersToCheck, IEnumerable`1& possible)
   at PKHeX.Core.SaveFinder.FindMostRecentSaveFile(IReadOnlyList`1 drives, String& error, String[] extra)
   at PKHeX.WinForms.Main.DetectSaveFile(String& path, SaveFile& sav)
   at PKHeX.WinForms.Main.FormLoadInitialFiles(String[] args)

Loaded Assemblies:
--------------------
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll

PKHeX, Version=20.10.10.0, Culture=neutral, PublicKeyToken=null
C:\Users\Rayray\Downloads\PKHeX (201010)\PKHeX.exe

System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll

System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll

System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll

PKHeX.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null


System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll

System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll

System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll

Accessibility, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Accessibility\v4.0_4.0.0.0__b03f5f7f11d50a3a\Accessibility.dll

PKHeX.Drawing, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null


--------------------
User Message:
An error occurred while attempting to auto-load your save file.

I get this error when booting up PkHex. This started happening at some point at seemingly random when I was using the previous version. After updating, the error still persists. Any help would be appreciated!

Link to comment
Share on other sites

System.IO.IOException: The filename, directory name, or volume label syntax is incorrect.
An error occurred while attempting to auto-load your save file.

 

Should be enough information to indicate that one of your drives has a bad file. Try running the dev build to see what the error message says, it might help indicate what folder has the bad files.

https://projectpokemon.org/home/files/file/2445-pkhex-development-build/

Link to comment
Share on other sites

7 hours ago, Kaphotics said:

System.IO.IOException: The filename, directory name, or volume label syntax is incorrect.

An error occurred while attempting to auto-load your save file.

 

Should be enough information to indicate that one of your drives has a bad file. Try running the dev build to see what the error message says, it might help indicate what folder has the bad files.

https://projectpokemon.org/home/files/file/2445-pkhex-development-build/

...Oddly enough, I don't receive any errors running the dev build. It works just fine with it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...