$FW39Dir = "$($adtSession.DirFiles)\n4buj23w"
Start-ADTProcess -FilePath "$FW39Dir\WINUPTP.exe" -ArgumentList "-s"
results in this:
LaunchInfo : ProcessLaunchInfo { FilePath = C:\WINDOWS\ccmcache\2o\Files
4buj23w\WINUPTP.exe
I realize this has double quotes but why would it replace the \n with a Line Break?
Nerd
If this is causing an error, It's because the \ is an escape character for many languages.
And \n is an escape sequence for .. new line.
I would just rename the \n4buj23w\ folder and avoid the issue.
That's annoying dude.
Agreed it's annoying. Can you please report this as an issue on our GitHub? A path shouldn't have it's directory separators be treated as character modifiers.
Actually @Nerd_Help, is this breaking things, or just breaking the string representation of ProcessLaunchInfo in the log output? This doesn't seem to be causing a real-world issue at all
Looking more thoroughly at my logs it is only breaking output of the log and not the execution of the process. I had a failure in the log, but it was successful execution with Exit Code 1. I wasn't handling that properly, once I accounted for a Successful exit code 1 things flowed.
I had renamed the directories earlier and also added the Exit code about the same time and didn't put it all together until now.
Thanks for the response, you guys rock!
Lesson is, read the entire log entry. Slowly. Twice.
