error message 1828.k.no.nt on every single action

**mjindustry** · 01 December 2011, 02:45 PM

Anyone ever seen this error message?

1828.k.no.nt

I'm getting it for every single action I try in Xara Photo & Graphic 6

**gwpriester** · 02 December 2011, 01:04 AM

What happens if you shut down and then reopen the application?

I've found that often the program gets a wild hare up there and shutting down and restarting frequently gets rid of the problem.

**wizard509** · 02 December 2011, 04:46 PM

Originally Posted by gwpriester

What happens if you shut down and then reopen the application?

I've found that often the program gets a wild hare up there and shutting down and restarting frequently gets rid of the problem.

I find that helps too. Not just with Xara but with many progs.

**mjindustry** · 05 December 2011, 05:17 AM

Thanks guys...happening every session. Even after system reboots. hmm.

Maybe I need to reinstall?

Another problem I would like to get sorted out is my "Designs Gallery" clipart etc...never will import into my project. It's their on my system, but says not yet installed and to go install it.

Maybe a new install fixes these two problems... What you guys think?

**PhilM** · 05 December 2011, 06:03 AM

Make sure that the problem isn't in a particular document before you try re-installing.

Close all documents, exit the program, restart the program and then try the actions that were producing the error message before.

Phil

**angelize** · 05 December 2011, 06:06 AM

Are running a registered version or a trial? The designs gallery behaviour you describe suggests a trial, but still you shouldn't be getting errors like that even with a trial version. Try re installing and if that doesn't work post back here maybe someone may be able to help.

**mjindustry** · 07 December 2011, 02:25 AM

Well it stopped. Right after I installed the demo for 7!

Opened up 6 and the error was gone. Now to decide if I want to keep 7 or not...

**Scotty** · 07 December 2011, 03:06 AM

Hi,
I get a similar error after doing a windows update and not doing a cold boot, It usually goes away after a cold reboot. I think it may be related to windows updating the C++ section of windows.
Jim
p.s. Just my thoughts and suggestion