Need help with IF EXISTS, THEN Statement

spiceuser-daoaa · 2019-08-30T20:51:29.000Z

IF EXIST ( "E:\netprofile.xml" ) 
                begin
                  CMD.exe netsh wlan add profile filename="E:\netprofile.xml" user=all
                  
                  else

Neally · 2019-08-30T20:59:25.000Z

If you post code, please use the ‘Insert Code’ button. Please and thank you!

PLEASE READ BEFORE POSTING! Read if you're new to the PowerShell forum! .

Neally · 2019-08-30T21:00:36.000Z

you can just use ‘test-path’

if(test-path "E:\netprofile.xml"){
    #do stuff
}
else{
    #do other stuff
}

spiceuser-daoaa · 2019-08-30T21:10:00.000Z

When I put in code:

if(test-path "E:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="E:\netprofile.xml" user=all}

It spits out this:

"E:\netprofile.xml"){ was unexpected at this time.

Neally · 2019-08-30T22:04:34.000Z

Looks like it might be cutting parts of it off? what version of powershell are you using? you are pasting that into a powershell session?

Have you tried to save it to a .ps1 file and execute it like that?

spiceuser-daoaa · 2019-08-30T22:17:44.000Z

I’m pasting it directly to powershell like that… [Version 10.0.18362.295]

spiceuser-daoaa · 2019-08-30T22:24:29.000Z

Capture.png800×234 67.5 KB

It seems like its doing an odd behavior, it gives a different answer the first and the 2nd time it is run

spiceuser-daoaa · 2019-08-30T22:34:58.000Z

The end goal is to open that file, should it exist on any of these drives:

cmd if(test-path "D:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="D:\netprofile.xml" user=all}	
									else 
								if(test-path "E:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="E:\netprofile.xml" user=all}
									else
								if(test-path "F:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="F:\netprofile.xml" user=all}
									else
								if(test-path "G:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="G:\netprofile.xml" user=all}
									else
								if(test-path "H:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="H:\netprofile.xml" user=all}
									else
								if(test-path "I:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="I:\netprofile.xml" user=all}
									else
								if(test-path "J:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="J:\netprofile.xml" user=all}
									else
								if(test-path "K:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="K:\netprofile.xml" user=all}
									else
								if(test-path "K:\netprofile.xml"){ CMD.exe netsh wlan add profile filename="L:\netprofile.xml" user=all}
									else

psophos · 2019-08-31T00:27:25.000Z

spiceuser-daoaa:

I’m pasting it directly to powershell like that… [Version 10.0.18362.295]

Pretty sure that version is for a cmd shell and not powershell.

jitensh · 2019-08-31T01:29:04.000Z

if you want it to work in Powershell simply remove cmd.exe

Evan7191 · 2019-09-03T11:38:05.000Z

M Boyle:

spiceuser-daoaa:

I’m pasting it directly to powershell like that… [Version 10.0.18362.295]

Pretty sure that version is for a cmd shell and not powershell.

I agree. Also, the error message is not like most Powershell errors.

dannease · 2019-09-04T13:48:09.000Z

JitenSh:

if you want it to work in Powershell simply remove cmd.exe

Agreed. What seems to be happening is that you start off in Powershell, but as soon as your script calls cmd.exe you drop into a command prompt and you’re no longer in Powershell at all, which is why you get two different behaviors. Notice how your first prompt has PS in front of it, but the second one doesn’t? Cmd.exe never exited (probably because you forgot the /c argument to tell it you were passing a command), so all you really did was launch a cmd prompt. The second time you pasted your command, you essentially pasted a PS command into a CMD prompt. No Bueno.

Instead of calling CMD, you could just try running netsh from PowerShell directly. However, I think putting the whole thing into Invoke-Expression is a better approach:

$command = 'netsh wlan add profile filename="E:\netprofile.xml" user=all'
Invoke-Expression -Command $command

I haven’t tested that so no guarantees, but I think that’s the right approach at least.