I don't see anything that looks like a relevant error in the nwsapsetup log; it appears the installation itself went fine. You aren't on the latest patch of sapsetup, but the patch you're on should be ok, and in any case it looks like the error occurs later. The only part that's a little odd is that it looks like you are doing an installation via a package defined on an installation server, yet the installation server path appears to be in your local temp files. Perhaps I'm misreading something about this. Normally, when installing pre-defined packages to multiple workstations, the preferred way to do this is to setup an installation server and then to run the install on each workstation from there. The other part that stuck out for me is that you are installing a package with a great many optional components included. Do you really use all those add-ons? If not, you can simplify your SAPGUI distribution considerably by reducing the number of components in your package to just the minimum required. As an example, in the package we distribute to users, we include only SAP GUI, SAP Logon, GUI XT, SAP Automatic Workstation Update, and SNC Client Encryption. Some of the optional components have dependencies on non-SAP Windows components that may or may not be installed on the workstation.
From the other logs you supplied, again, I don't see an obvious error. At this point I'm suspecting it isn't actually anything to do with your SAPGUI installation, but something else is going on with this workstation. I would check it thoroughly for malware and/or unneeded programs, using tools like CCleaner, MalWareBytes, SpyBot Seach & Destroy, GMER, etc. And run a full virus scan with your preferred antivirus tool.
If that doesn't help, then my next suggestion would be to open an Incident with SAP Customer Support, and/or to ping Jude Bradley on this thread.