Paraglider

VMWare released version 14.1.8: https://docs.vmware.com/en/VMware-Workstation-Pro/14/rn/VMware-Workstation-1418-Pro-Release-Notes.html with this fix: Unable to run VMware Workstation Pro / Player 14.x after updates on Windows 10 1903 VMware Workstation Pro and Player versions 14.x and earlier failed to launch on Windows 10 1903, after Windows 10 KB updates were applied.

MS posts a list of problems. See: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903

I have upgraded 3 laptops, 1 desktop and 4 VMs to 1809 build from the 1803 build. All have upgraded without problem.

I think its all the junction points that are the issue in mounting. They all are rebased to point at the mount folders. If you look at the extracted folders from a se build the junction points don't work.

It would be nice if the syntax check log included the line number of the line in the script.

Another compatibility issue with RegWrite: RegWrite,HKLM,0x7,"Tmp_Software\Safer Networking Limited\Spybot - Search & Destroy 2","Download Directories" reports this error: [1/2] Invalid RegWrite Syntax (RegWrite,HKLM,0x7,"Tmp_Software\Safer Networking Limited\Spybot - Search & Destroy 2","Download Directories") If you export the key with regedit I see: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Safer Networking Limited\Spybot - Search & Destroy 2] "Download Directories"=hex(7):00 Or in unicode format: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Safer Networking Limited\Spybot - Search & Destroy 2] "Download Directories"=hex(7):00,00

This: If,NotExistFile,"%SourceFolder%\testdisk_win.exe",Run,%ScriptFile%,Halt reports this error [1/1] Wrong branch condition [NotExistFile] (If,NotExistFile,"%SourceFolder%\testdisk_win.exe",Run,%ScriptFile%,Halt) I have all compatability optons checked.

I have found a number of incompatibilities so far: In strings winbuilder supports "" as a double quote escape character as well as #$q Winbuilder does not require a description= line in main Winbuilder supports a not prefix e.g. NotExistDir as well as Not,ExistDir. This seems to be supported for all Exist variants.

Seems like syntax checker does not report the actual error any more when a script is referenced through a link file: 1 syntax error detected at [Win10PESE\Addons.PG\Pwdsafe\PasswordSafe.link] [1/1] Syntax error () Section Coverage : 100% (6/6)

Thanks. That fixed it. Getting closer to my modified version of win10pese working.

Note I have the winbuilder help online here: http://wb.paraglidernc.com/Help/default.html

I still cannot get existregmulti to work. I get a script error from this: if,not,ExistVar,HKLM,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,begin RegWrite,HKLM,0x7,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,hotcore3 end else,begin If,not,EXISTREGMULTI,HKLM,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,hotcore3,begin RegMulti,HKLM,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,APPEND,hotcore3 end end 2 syntax error detected at [Win10PESE\Addons.PG\HDM15Pro\hdm15pro.link] [1/2] Wrong CodeType [Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}], Only alphabet, number and underscore can be used as CodeType (if,not,ExistVar,HKLM,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,begin) [2/2] Cannot parse Section [SetupReg.AddReg] : Else must be used after If (else,begin) Section Coverage : 100% (6/6)

I got a permanent ban ( and an ip block ) there as well for mentioning script a second time.

Did not fix this one though which I fixed by changing the win10pese script: Search plugin fails inside the macro library called by this script line: Call,FileCopy,%Source_sys%\prm*.dll,%Target_Sys% Although there seems no need to use Call. I changed to: FileCopy,%Source_sys%\prm*.dll,%Target_Sys%

Probably could debug it myself. Already temporarily fixed a bug to remove dependence on Main containing a description line which I reported to the author.

They were converted from the output of regshot using my own reg to winbuilder script tool.

Some of my own personal scripts for commercial products. First one was for Paragon HDM15 Pro. Second for Passmark Performance Test 9.

This line also passes the syntax check but fails at build time: RegWrite,HKLM,0x3,Tmp_Software\Classes\CLSID\{LNINEVST-4YBM-7IPO-BXF1-KZLBS2X3NP70},0,\ 44,44,28,F6,EF,7C,37,94,04,B5,BF,68,D8,94,BA,93,1C,55,26,62,4C,BC,70,\ FA,20,6A,86,68,6B,6D,05,57,1A,D3,3F,59,8E,8C,60,92,52,E1,28,62,3F,6C,18,71

ExistRegMulti is also not supported: If,ExistRegMulti,<HKEY>,<Section>,<Key>,<SubString>,<Command> The command checks for the existence of a substring in a multiple string REG_MULTI_SZ registry value. Such a registry value contains a sequence of null-terminated strings, terminated by an empty string (\0). Usage: If,EXISTREGMULTI,HKLM,SYSTEM\ControlSet001\Control\ServiceGroupOrder,List,"FSFilter Infrastructure",Echo,YES Or how I use it: If,EXISTREGMULTI,HKLM,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,RegMulti,HKLM,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,APPEND,hotcore3 Else,RegWrite,HKLM,0x7,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,hotcore3

Original winbuilder was no longer supported. PEBakery is far superior to original builder. The author of PEBakery has done a fabulous job in writing a replacement. If you don't like PEBakery then don't use it. I agree the winbuilder scripting language should never have been invented as at the time there were many superior alternatives. However it was and we now have several active projects that use it. Its great that those of us that still use those projects have a supported actively developed alternative to the original winbuilder.

Yes. Cmd language is very powerful and has many features that are hard to use. I am a professional software developer and have written many batch files over the years to aid in the software development process. I am slowly switching to powershell. Tasks that required console apps to be written now can be done totally in powershell. The powershell debugger is great and makes powershell script debugging a lot easier than debugging cmd scripts. If you are writing batch files for windows pe then .cmd / .bat scripts are preferable due to the .net overheads of powershell.

Powershell command prompt still supports console applications. Any console applications that run in cmd.exe will still run in powershell cmd line. Ipconfig is an external console application so runs exactly the same in a powershell command line as it did in cmd.exe. If you want to switch powershell prompt to a cmd prompt just type cmd.exe /k. Cmd.exe is not being removed from windows 10 just the default is being changed. Its very easy to switch back to cmd.exe as the default - just go to settings / taskbar. I think you will find most windows users never use a command prompt. Those that do will easily be able to switch back to the original default if they are not happy with the change.

Not true. Still 2nd august here and I have downloaded 1607 from windows update, MSDN, and via the windows 10 media creation tool.

It will default to your local user. Replace with your ms user account information.

Run netplwiz and uncheck 'Users must enter a user name and password to use this computer'. Press Apply and enter user name / password when prompted.