The issue you are experiencing could have to do with some sort of proxy that you have installed on your Mac as one of the other comments in response to your thread indicates. In that respondents case, his company was routing all his traffic through a proxy, and thus when s/he left the office and went to a Starbucks, where the proxy wasn't present, s/he was able to install the patch. My case was a little different, but also related to proxying software.
I have a corporate issue MacBook Pro 15" running High Sierra 10.13.6. Whenever attempting to use the Mac Store app to apply the 10.13.6 supplemental updates (including iTunes 12.8, Safari 12.0.1, and Security Update 2018-002 10.13.6) it would fail during the installation phase with "An error has occurred. An error occurred installing the update. (602)". It has been very difficult to find any concrete answers to this question online, and I ultimately used the Console app on the Mac to provide me with some clues as to what might be happening. This row from my Console log shows the failure, and the primary clue for me was that NetworkRequired = true.
Operations failed with error: Error Domain=BOSErrorDomain Code=204 "An error occurred during preflight." UserInfo={NSLocalizedDescription=An error occurred during preflight., NSUnderlyingError=0x7fb369224b50 {Error Domain=BridgeOSSoftwareUpdateError Code=19 "MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);AMAI - 3099 (AMAuthInstallBundlePersonalize() failed: );" UserInfo={NSLocalizedDescription=MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);AMAI - 3099 (AMAuthInstallBundlePersonalize() failed: );, MSUErrorCode=2, AMAuthInstallErrorCode=3099, MSUErrorDescription=Failed to personalize with options., NetworkRequired=true}}}
Additionally, I saw a number of other rows above this one in my console log from a bosUpdateProxy process that was brokering TLS handling (managing data encryption). The big "ah hah" for me was that I had proxy interference, further substantiated by the Starbucks respondent, so I started digging around on my Mac for proxying software, and came upon a new app/service that my company uses called Zscaler.
I was thankfully and with great relief able to solve the issue by setting the Connectivity Status of the installed Zscaler application on my Mac from "On" to "Off" (I did not uninstall it -- just turned it off) and then trying the install through the Mac Store App again. Once it was "Off" I was able to install the supplemental update software successfully to my Mac.
I hope this helps you or someone else suffering from the same problem.