www.wysiwygwebbuilder.com

Hi Pablo ... sorry to bug!

Never had this happen before and I can't seem to figure it out.

Trying to install 18.4.0 (Sept 22 build) - 64-bit

I have WIndows 11 ... all applications updates are current.

I know WWB is not malicious but NORTON is going goofy!

I have disabled in my NORTON 360 Deluxe
- AUTO-PROTOECT
- SMART FIREWALL

BUT I still get TREATS BLOCKED ...

... it won't get past ..\splashscreen.png

I have attached an image of the errors

Have you tried to simply disable Norton altogether, install it and then turn it back on?

This is a false positive from your AV (Norton) program as there is no Malicious code in the program!. Please add either versions 32/64bit to the list of execeptions of Norton to resolve. The reason that this happens is because of the update has a slight change in the code over the previous version and Norton sees it as a threat when it is not. As mentioned simply add WB to it exceptions (whitelist) and all should be good.

Thanks crispy68 and BaconFries for you input ...

This was my fix ... for others who may experience this.

When attempting to install WWB the NORTON WARNING shows:
"Data protector blocked a suspicious action by setup64.tmp"

Google search indicated these steps

Open Norton > from Dashboard click the Device Security OPEN button

Click SETTINGS in menu bar

Click ANTIVIRUS

Click DATA PROTECTOR tab

Turn OFF Data Protector

Click APPLY

Click 15 minutes button

Then Install WWB as you normally would ...

Once done ... turn Data Protector back on

Thanks for sharing your solution!

I've also had the same problem trying to update to WWB 18.4 as described above.

I followed the precedure suggested by cmsintent which worked as described - thank you.

While researching the problem online, I discoverd that to prevent this happing again with the next wwb upgrade, the file 'WebBuilder.exe' file needs to be added to Norton Exclusions (whitelist). I found the procedure to do this at https://knowledge.civilgeo.com/knowledg ... -firewall/.

Thanks again to all for posting the fix to this problem.

Roy