Fix VB.NET-Batch Integration

The hand-off between my VB.NET desktop application and the Windows batch script it spawns is breaking down. Calls that should complete cleanly either hang, return the wrong exit code, or pass back garbled data, so the .NET side never receives the signals it needs to continue processing.

I need you to step through both ends of the chain, identify exactly where the handshake is failing, and implement a clean, well-commented fix. You may touch either the VB.NET code, the .bat file, or both—as long as the two pieces finally talk to each other reliably on Windows 10/11.

Please send a concise, detailed project proposal outlining
• how you will trace the interaction,
• which debugging tools or logging you plan to use (e.g., Process.Start diagnostics, echo/exit-code tracing, Visual Studio debugger, Sysinternals), and
• the estimated timeline for delivering a tested solution.

Deliverables
– Corrected source code for VB.NET and/or batch script
– A short change log explaining what was fixed and why
– Proof-of-fix: screenshot or log output demonstrating a successful loop of launch → execute → return code → VB.NET confirmation

I will compile and test the updated solution immediately on receipt and sign off once the integration runs end-to-end without errors.