That sounds like the problem. At this time, you need to download and use the 32-bit installer.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: sr8283 on May 17, 2021, 11:28:54 PM
Hi PMPC,
We have similar concerns over the auto update of the apps which we want to test before rolling it out to production. Is there any article or guide that we can refer to for cases like this?
Appreciate any help provided. We are now running the trial version of PMPC - 1 week old
Quote from: Atreus21 on March 02, 2021, 06:49:10 PM
I looked at the KB for this issue as well as followed the video but I'm confused. I've never stood up a separate software update point as the video suggests as a possible cause.
The registry entry cites J:\WSUS, which is the SQLTempDB volume. I've absolutely no idea how it got there. It's also got nothing in it beyond two folders WsusContent and UpdateServicesPackages.
The SQL query cites G:\WSUS, which I think is where it's supposed to be. That's the Content Source volume, and it's definitely got lots of contents, clocking in at three quarters of a terabyte.
The IIS Basic Settings cite C:\Program Files\Update Services\WebServices\Root as the physical path.
When I run the wsusutil.exe to specify G:\WSUS, it tells me:
Content location is being moved. Please do not stop this program.
Content move failed. Please refer to the log file for more details.
Fatal Error: The new content file location is the same as the old location: G:\WSUS
Parameter name: newContentPath
Should I move it somewhere else?