Having trouble understanding this program

I opened the program and it seems to be doing the same thing it shows a girl with Daz 4.9 on it and it says below upgrading CMS; but its been doing that for a bout an hour now. Is it supposed to do that?
You currently have no notifications.
I opened the program and it seems to be doing the same thing it shows a girl with Daz 4.9 on it and it says below upgrading CMS; but its been doing that for a bout an hour now. Is it supposed to do that?
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
What your system specs? Windows? What version? Mac? Other? Are you running any security software that might be blocking the CMS (Content Management Service) from accessing DAZ?
If you have a lot of content, yes it can take a while. This has been mentioned in the release threads and the FAQ for quite a while.
I have McAfee I have Windows 10
Have you let the program run for awhile to see if what Chohole has suggested is the culprit?
The first thing that we should do is check the DAZ Studio log file to see if that provides some insight. The log file can be found here:
C:\Users\yourusername\AppData\Roaming\DAZ 3D\Studio4\log.txt (yourusername is of course your actual username, whatever that might be)
It is also available from within DAZ Studio, but it is cumulative and can be quite long, so we need to address that first.
Open the log.txt file from the location indicated above, select all the text within the file and delete it (the selected text, not the file). then simply save the empty text file. This will give you a nice, clean log file that will be easier to read. Then open DAZ Studio and let it run for a bit to ensure we capture the issue. Now close DAZ Studio and go back to the log.txt file and attach a copy of that to a post here so we can have a look at it.
If that doesn't help us solve the problem, then we can go to Plan B.
Are you installing your content manually or with DIM?