Mdt 2013 refresh wizard canceled as soon as I authenticate

Question

I've been after this for a week or so now. I'm trying to run a POST OS Installation task, something I've done many times before, but always in MDT 2010. I"m now trying to kick off MDT 2013 from Windows 7 x64, and I get as far as being prompted for credentials.
As soon as I enter my credentials, MDT quits and cleans up, immediately. Literally 1 second later according to the BDD.log. Nothing unusual seems to be recorded in the logs.
If I try to run it again without deleting the MININT folder, it usually succeeds. If I then cancel out of the Task sequence menu without choosing anything and try it again, it fails again. Is this some type of bug? I've googled extensively, can't find anything.
I've removed all software that has been updated recently from the PC, no AV is installed, nothing that should be stepping on anything.
I'm running from an elevated prompt, like so:
\\Server01\Deployment01$\scripts\LiteTouch.vbs
Bdd.log returns this:

Answer 1

just to loop back here... I replied to Joe offline via E-Mail. the case is very weird:
I think it may have to do with the EVENTSHARE being defined in the bootstrap.ini file, somehow that is forcing MDT to setup a new connection to
\\Server\Events$  and the dialog prompting for credentials is causing problems.
*Still* that shouldn’t case this code to return true:
' Was the wizard   cancelled? 
If so, exit
If UCase(oEnvironment.Item("SkipBDDWelcome"))
<> "YES"
and oEnvironment.Item("WizardComplete")
<> "Y"
then
Cleanup
oLogging.ReportFailure "Welcome wizard failed or was   cancelled",
5212
End
if
The logs *SHOW* that SkipBDDWelcome and WizardComplete are set properly:
Property SKIPBDDWELCOME is now = NO            
ZTIGather           
12/18/2014   8:45:14 AM  0 (0x0000)
Property WizardComplete is now = Y     
Wizard  12/18/2014   8:45:15 AM 
0 (0x0000)
Might be some kind of weird race condition in the Litetouch.wsf code. The progress bar UI fluff is pretty complex.
My recommendations would be to place EVENTSHARE into the cs.ini file rather than the bootstrap.ini file to see if that fixes things.
Otherwise just commenting out the code above, I’m not 100% sure why it’s there to begin with.
-k
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com