check the USB-C cable connection to your USB port, try with another USB-C cable -> I can do it, with another cable of mine, as soon as possible
verify the integrity of the game file ->
--------------------------------------------------------------
Application starts at 26 agosto 2022 13:48:50
Reading keys
- prod.keys (exists)
- title.keys (exists)
- console.keys (not exists)
Found 1 title keys
Reading version list
Initialization success
Open Directory
6 files selected
Processing file E:\NS\nut\titles\Donkey Kong Country Tropical Freeze[0100C1F0051B6000][v0].nsp
in NX_Game_Info.Process.processFile(String filename)
File E:\NS\nut\titles\Donkey Kong Country Tropical Freeze[0100C1F0051B6000][v0].nsp has failed to process
check the SD card for errors, when installing via MTP ->
Warning: Only 59235 of 59632 MByte tested.
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 24.8 MByte/s
Reading speed: 82.7 MByte/s
H2testw v1.4
The warining is related to sd card is not empty (stuffs related to CFW), I guess
try to run DBI in application mode (title override) holding the R button while launching a title -> not possible, no title installed (the very first time it is a normal scenario)
Really strange behaviour! I just installed a bunch of nsz/nsp files myself via DBI MTP responder, and everything went super smooth -> It would be interesting check my environment against your files...is it possible to know where nsz/nsp files come from?
We should concentrate on making NX_Game_info work on your system.. It seems to be choking for some reason, on your end. When I run it on Linux here (command line interface version), I get something like this:
wine nxgameinfo_cli.exe /home/Dust2dust/Documents/switch/PictoQuest\[010043B00E1CE000\]\[v0\].nsp
NX Game Info 0.7.1.0
Copyright © 2018-2019 Garoxas
Opening file /home/Dust2dust/Documents/switch/PictoQuest[010043B00E1CE000][v0].nsp
/home/Dust2dust/Documents/switch/PictoQuest[010043B00E1CE000][v0].nsp
├ Title ID: 010043B00E1CE000
├ Base Title ID: 010043B00E1CE000
├ Title Name: PictoQuest
├ Display Version: 1.0.0
├ Version: 0
├ Latest Version:
├ System Update:
├ System Version: 8.1.0
├ Application Version:
├ Masterkey: 7 (7.0.0-8.0.1)
├ Title Key: 0CE575727559BA12A175C45656A586DA
├ Publisher: Plug In Digital
├ Languages: en-US,fr,de,es,it,ru
├ Filename: /home/Dust2dust/Documents/switch/PictoQuest[010043B00E1CE000][v0].nsp
├ Filesize: 410.45 MB
├ Type: Base
├ Distribution: Digital
├ Structure: CDN
├ Signature: Passed
├ Permission: Safe
└ Error:
1 titles processed
So on Windows, it should be
nxgameinfo_cli.exe **full path of your nsp file** (not including the **)
You enter that in a command prompt (that black window thing) and the command prompt should be opened in the same directory where nxgameinfo_cli.exe is located. Don't forget to also include a fresh prod.keys in that same directory. Once you get it working, it should help you to verify all your nsp files. The most important info is Structure, Signature and Permission. CDN means originally downloaded from eShop, Signature passed means it hasn't been tampered with, and Permission Safe means it won't do nasty stuff to your console.
My nsp/nsz files come from a variety of sources, some more trustworthy than others, but when I'm in doubt, a quick check with nx game_ info is enough to reassure me.