Hi Collin,

Where did you get the PU2 from? I got mine from this link: https://dlm.esd.sage.com/d.aspx?_C=185a6941-a874-4827-8ef5-1474ef2d8650. Once it downloaded, I right clicked the file, viewed properties, then on the bottom right, checked the unblock box, then apply then ok, before right clicking it to run as administrator. 

Afterwards, I had to re-install / update WSSetup for all of my end users.

Hi Vanessa,

I downloaded from the Partner Portal via the knowlebase here:

https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=115299&sliceId=1&docLink=true&languageId=&isDocLink=true&currentmsID=MS_Customer&cmd=&openedFromDocument=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl 

Hi Collin,

So, have you checked the downloaded file properties to see if it's blocked (Windows Defender / Smart-screen has been doing that to almost all executable files that are downloaded)? Have you tried to temporarily turn off antivirus or firewall before running? All users are logged out of Sage during your attempt to run of the PU2?

I downloaded and ran mine from C:\Temp on our server...after temporarily turning off antivirus + firewall and unblocking the file. Haven't seen any Sage PU stuck like that before with Sage 2022 but with Sage 2019 I had the problem with PU1, 2, 3 & 4 and that's what I did with each one to get the PU to actually run and complete. I'm definitely not an expert on anything Sage, just suggesting this from lessons learned with Sage PU's so far. :)

Vanessa,

Thanks for your input again.

In this case, the install is been done on a standalone for testing purposes and the file is not been blocked either via firewall or antivirus.

PU1 was installed without any issues, and then PU2 will not complete. 

I downloaded using your link and the same issue again. 

Maybe something to do with the Wen Screens, because that is where it again hangs up.

Collin,

Oh I didn't realize it's a standalone test environment. :) You're definitely smarter than I am in your approach then. I did mine after operation hours on our production server (of course with a server backup / restore ready to go).  

Have you tried to do a repair install to Sage itself, reboot and then maybe try to run the PU2 again afterwards?

I'm sorry I'm not much help...

Vanessa,

For now, have rolled back to PU1 as this was the 3rd attempt at getting it to load.

Did a uninstall of Sage 2022 Reboot, reinstall, reboot, then PU1, reboot PU2 and all that still fails.

Unfortunately unable to spend any more time on it just now.

If you are installing from a network drive/share, you might want to try copying the PU locally and installing from there.

Otherwise, when it seems to freeze, Alt-Tab and see if there are any messages awaiting input. Sometimes there's a Visual C++ redistributable message hiding back there.

Team Equations,

In this case it's all local and there were no other popups in the background... Ensured it was the only thing running at the time  (at least the second time round )

So any popups would have been visible.

Cool. And you were running as administrator? The user installing was a local machine admin? 

Maybe try temporarily disable UAC as well.

Hi, I did not have an issue installing Product Update 2 in a standalone test environment. Did you turn off anti-virus protection? Also make sure to run Regacc.exe as Administrator when you are finished because not all of the dlls are getting registered with Product Update 2.

Hello Suegeek,

Antivirus is off and you would recognise regacc does not apply as the installation cannot be completed.

Hi Collin, Sorry was in a hurry with my reply. I would try Regacc before installing Product Update 2. Once Product Update 2 is successfully installed I was just giving a heads up to not forget to run Regacc otherwise it may not work with 64-Bit Office.

No worries, Regacc before after PU1 was done and did not help at all.

You're heading into format D land soon, I think. But here are some things that I thought about:

Is the path where your Sage is installed particularly long so that the full path including that file is more than 260 characters?

Is there a log file of the installation process that you can look at?  (This might need tech support to chime in.)

You did a full un-install I see.  There's no need to install PU1 and then PU2 - if you try a re-install (and I would install to a different folder structure), just do the main install and then PU2.

What version of Windows are you installing on?  32 or 64 bit?

How's the hard drive space on the D drive?

 Django,

Formating is the last place I wish to go...

The path is OK, 2022 PU1 was running quite OK from it

Windows 10 64Bit 
Drive D has 559GB Free so not a space issue I think.

Were you running web screens on it before?

Web Screens were occasionally used, but not on consistent basis

Maybe try stopping IIS before the installation?

I'm curious to know what renaming the file will do as well.

Renaming what file?

Stopping IIS did not help.

Went on to do clean uninstall, restart, new installation on new drive and restart, then start to PU2 and same issue.

So I think I will pass on PU2.

I was referring to renaming the file that the process was held up on from your screenshot.

I'll clone my 2022 PU 1 virtual and try installing PU 2 later today and see if I have the same issue.

Django,

The only issue would be that it did not always stop on the same file...

Ah - okay - I missed that part.

Update:

I have narrowed down the issue to be specific with Web Screens.

Did a uninstall/reinstall without web screens and went direct to PU2 and that was installed without any issues.. so it is definitely a web screens issue.