[2004, 20h2] Core Draw issues : NTUSER.dat and HKEY_CURRENT_USER\Software\Corel\

[kennysarmy]

Just had a remote session with Corel Draw Business Support.

 

I've just sent them a summary of the call which is :

 

Thanks, Simone, for the remote sessions earlier so we could show you the random problems we're getting with Corel Draw not opening correctly for some of our users.

 

I understand from our conversation that other institutions in the past have had similar issues, but that there is not yet a fix from Corel?

 

You explained that you believe the issue is related to the loading of the file C:\Users\Someuser\ntuser.dat into the HKEY_CURRENT_USER part of the registry, specifically the entry which populates into HKEY_CURRENT_USER\Software\Corel\CorelDRAW\23.0\IPM_CDGS

 

I've sent you two registry exports of key IPM_CDGS from HKEY_CURRENT_USER one when logged on as a user where Corel opens fine and one from when the issue occurs.

 

I'm hoping from these two files you will be able to identify which exact line of the registry is missing or corrupt so we can put in a temporary fix.

 

However, a better solution would be for Corel to understand what is happening on the local machine to cause this issue and put a permanent fix in place.

 

 

I'm still not 100% as to what Corel checks at launch to know whether to open correctly OR to show the logon splash screen (Which it should not do)

 

 

We've done a server deployment which should mean the software just opens on launch, but for random users they get this splash screen:

 

 

Clicking Skip just closes the splash screen and nothing happens.

 

Corel believe this is related to the key : HKEY_CURRENT_USER\Software\Corel\CorelDRAW\23.0\IPM_CDGS

 

I understand this is populated from NTUSER.DAT.

 

But my question is how does the correct (or wrong) data regards Corel get in to NTUSER.DAT ?

 

If we delete the local profile for an affected user it will temporarily fix the issue, but it can return!

[kennysarmy]

 

 

Loaded a couple of Reg Hives from two users on the test PC (one working, one not).

 

You can see this part of the registry is different...wonder if this holds the key to the mystery.

[chazzy2501]

aww man good luck. Corel Draw 2020 deployment drove me loopy. The deployment instructions do not mention what version can do what deploy and the instructions allow you to mostly deploy using a method not supported by the version you purchased! (yes deployment methods are locked out depending on licence but is not documented)

[chazzy2501]

To me it looks like a deployment issue. The registry stuff looks like a symptom (not a cause) made from install issues. There is a don't badger the user option in the deploy.

[kennysarmy]

Useful from COREL 3rd line support!

 

 

Have you found out the differences between that group where the other user belonged to? He must have had something different compare to the first user.

 

The problem is as I said not related to CorelDRAW but the way how these users are integrated into the system.

 

Thank you,

Simone

Corel Customer Support

 

Err no - they are all standard student accounts - all exactly the same!!!

Must be a bug in your software?

 

 

 

It's no bug in our program, but there was something different in the approach to install the program and when the students launched it the first time.

 

Let's say it in that way: I get a lot of those companies with servers and they all manage it. In other words, there must be a way to get this done from a view of IT.

 

Thank you,

Simone

Corel Customer Support

 

Please can the call be upgraded to second line support?

 

 

It's not about how they open the program: it's all about what version they got installed (seems to be from the server image), and what profile they use.

If they are all users, then it might be the reason that they have limited permissions to add content to the registry.

 

What server do you use? And do you use cloned systems?

 

What your request regarding a second line support concerns, I'm the third and last level and do this job for more than 10 years now.

Our support is not about helping in a network environment as these are parts of the company's own department, or as our IT admin used to say when I naively asked him 10 years ago, "how do you deploy", and he said, "boa, Simone, there are so many ways to do it, each IT has got its own way".

 

Everybody who contacts us in such issue "want to deploy", ends on my table and all I need to provide is the information to use a server image.

In 99%, I only get a final reply form them, "issue is solved, close the ticket".

 

As I said yesterday, this is what other ITs mentioned:

"when the users started with USER accounts, they were not able to avoid the sign in window, we had to change to an Administrator account"

Note from my side: I installed from a server image in my VMware into an admin account -> created a USER account -> launched Draw in that USER account and I was not asked to sign in.

Conclusion: there must be something different between a corporate USER and my ordinary Windows USER

 

 

Thank you,

Simone

Corel Customer Support

[kennysarmy]

You'll love their latest response!

 

Re:

When logged in as 7316 (application opens correctly) ... When logged in as 7305 ON THE SAME PC (

 

That means your endusers share the same PC now and then. You didn't tell me that on Monday during the session.

If that is the case, then the sign in request works as intended.

 

I'm going to contact the development team if they have another idea to solve that. The only solution I know is to edit the registry entry (what you had already done with importing the registry from the working user to the non-working user).

 

I had escalated this as an enhancement request last year since mostly companies work in shift with often 3 users on the same machine.

 

 

Thank you,

Simone

Corel Customer Support