Home › Forums › System Ninja Support › Bug found
- This topic has 84 replies, 7 voices, and was last updated 6 years, 4 months ago by
Shane Gowland.
-
AuthorPosts
-
Phobos
ModeratorThe Old Chrome Directory is not delete from the context menu, only using button the Delete Files.
Windows 11 Pro Insider, x64
Dennis Ekelund
GuestHi
On launching System Ninja or CCEnhancer my windows 10 build 10240, I get this error # 0xc00ce556, any help would be appreciated.
I have used both in windows 10 earlier builds without errors.
Shane Gowland
KeymasterOn launching System Ninja or CCEnhancer my windows 10 build 10240, I get this error # 0xc00ce556, any help would be appreciated.
Windows 10 issues will not be addressed until the release build is finalized.
Shane Gowland
KeymasterThe Old Chrome Directory is not delete from the context menu, only using button the Delete Files.
Thanks for reporting this. Fixed.
Anonymous
InactiveNew System Ninja 3.1 portable doesn’t open on win 10
Mysteriously last old portable version worked fine until I went to new 3.1 today.
Howard Pearce
GuestSystem Ninja falsely reports folder junctions (linked data/folders/files) as belonging to the Recycle Bin and deletes them.
Shane Gowland
KeymasterSystem Ninja falsely reports folder junctions (linked data/folders/files) as belonging to the Recycle Bin and deletes them.
Could you please post the paths of some of these erroneous detections?
Howard Pearce
GuestSome lines reported by Ninja 3.1.4 results — followed by actual path to junction folder STANDALONE on Drive D
COPY PATH reports the files as from Drive C – perhaps leading to the problem ?
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\desktop.ini {0.13KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\Config.xml {10.85KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\CrushLinx V1.2.exe {284.50KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\desktop.ini {0.14KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\dview-config.txt {30.13KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\dview.exe {2,296.00KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\EmptyFolderNuker.exe {340.00KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\FolderMenu.exe {273.26KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\launcher64.dll {40.50KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\7-ZipPortable.exe {213.52KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\help.html {5.92KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\readme.txt {0.17KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7-zip.chm {88.89KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7-zip.dll {54.50KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7z.dll {437.00KiB}
D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7z.exe {72.00KiB}D:\Install\Standalone\7-ZipPortable\App\7-Zip
C:\Standalone\7-ZipPortable\App\7-Zip\7-zip.chm
C:\Standalone\7-ZipPortable\App\7-Zip\7-zip.dll
C:\Standalone\7-ZipPortable\App\7-Zip\7z.dll
C:\Standalone\7-ZipPortable\App\7-Zip\7z.exe
C:\Standalone\7-ZipPortable\App\7-Zip\7z.sfx
C:\Standalone\7-ZipPortable\App\7-Zip\7zCon.sfx
C:\Standalone\7-ZipPortable\App\7-Zip\7zFM.exe
C:\Standalone\7-ZipPortable\App\7-Zip\7zG.exe
C:\Standalone\7-ZipPortable\App\7-Zip\descript.ion
C:\Standalone\7-ZipPortable\App\7-Zip\History.txt
C:\Standalone\7-ZipPortable\App\7-Zip\License.txt
C:\Standalone\7-ZipPortable\App\7-Zip\readme.txtShane Gowland
KeymasterSo if you delete a file in D:\$RECYCLE.BIN\ does it also delete the corresponding file in C:\Standalone\?
To my eyes, it looks like when a junction was created between C:\ and D:\, the files already extant in D:\ were simply moved to the recycle bin and replaced with symlinks. That should mean that the files in D:\$RECYCLE.BIN should be safe to delete. If files are in D:\$RECYCLE.BIN, they’re probably going to be deleted next time you empty the recycle bin, since the bin is really just a GUI for that folder anyway.
Howard Pearce
GuestYes, it seems to. Deleted the actual file than just the link.
I’ve had to restore that C:\Standalone library folder from my weekly True Image image backup.
-
AuthorPosts