Windows 10: Anybody Familiar with u32Jpg.fio???

I use a relatively obscure commercial product "Photoimpact Pro" for many of my photo editing needs. For the last couple of months, I've been unable to use the program on my main desktop; as it goes through the several seconds of initialization it consistently hangs "Initializing u32Jpg.fio". My four other Win 10 laptops run the program fine, and I recently discovered that the two other accounts on the failing desktop also bring up the program without incident.

So whatever this problem might be, it's obviously something associated with my account, not the overall software installation itself.

It seems that u32Jpg.fio is a Windows file, to my surprise, and not something that comes with Photoimpact Pro.

Obviously I've tried a heavy-duty removal and reinstallation of the program without improvement.

I can't find any references to this file in the registry.

Does anyone have any suggestions for how one tracks down an account-related issue such as this one? The usual internet research hasn't panned out, other than showing a tiny number of similar reports with no solution. Any informed advice would be more than welcome.

Art

:)

 

6151 - editing images

babdi,

Understood. No problem at all.

Is anybody else familiar with this 6151 issue?

Cheers

 

Task Manager

My Task Manager stopped working. I suspect it has something to do with the last Window 10 upgrade. Is anybody familiar?

 

Hi Art, you may have to rethink that u32 is a windows file.

This points to u32 being a Ulead Image Module, and ulead is a Chinese software co. that developed photoimpact. In 2006 Corel bought ulead systems and photoimpacts' demise started then, see near the top: Ulead Photoimpact

Why only the one account out of three is acting up? It may be corrupt or just have a different SID. To check the details in all accounts: https://www.tenforums.com/tutorials/...dows-10-a.html You might be able to change the one that's acting up to match.

If you're still having problems with the u32 file I would suggest re-installing photoimpact with: https://www.tenforums.com/tutorials/...dows-10-a.html it's a lot easier than fussin' with accounts.

Steve

 

Steve, forgive me but that went by a little too fast.

What do you mean by a "different SID"? Of course all the accounts have different SIDs; all but the final hyphenated node are identical and the last node is in the 50x series for the guest and system account, and in the 100x series for the three user (administrative) accounts. Just as I would expect. I guess I don't comprehend what a particular SID has to do with the use of this weird file in question.

 

Not a problem Art,
You are correct that there would be different SID's for the different accounts and my misspeak threw you off, my apologies.

I should have said SIDType, if you look at the Properties/Description block in Shawn's tutorial you'll see it listed 2nd from the bottom and also check the Status to see if your problematic account has any status other than; 1. OK . If "type and status" are different from the two that work okay, it may be corrupt and you should try to create a new one to test and/or replace it.

Related:
https://www.tenforums.com/tutorials/...dows-10-a.html

And check the "Related Tutorials" section at the bottom of any tutorial you're working with to see if there are any that may help with the problem you're working on.

 

Thanks for the clarification. Alas, that appears not to be the issue; it is 1 / OK.

 

You're welcome; Lets try these steps, test after each one if 1. works your done if not go on to 2. then 3. :

1.) When was the last time you've run a SFC /scannow? Since the u32 file is only acting up on one account and windows is having a problem loading it the sfc scan may fix the problem. There may be a problem with that account's system files and Photoimpact's (PI) hanging u32 file.

2.) Go into Control Panel\All Control Panel Items\Programs and Features wait until it populates then right click on PI and see if a context menu pops up allowing you to repair PI, hopefully it will.

3.) As a last resort, I'd reinstall Photoimpact (PI) in "Compatibility Mode", the link is in my first post.