The problem is likely the action, or the images, not Image Processor.
First question - have you modified the action in any way, that you know of?
Second question - have you tried running a batch of older images that you know have worked ok in the past?
Oh gee. That's been artificially enlarged a long way, hasn't it? That's really awful.
If you're going to print it, I suggest canvas. Canvas is more forgiving. But even then, I wouldn't go very large.
The little app should show the correct profile highlighted for the screen that it's on. So if you have its window on the laptop screen, it should have the laptop's profile highlighted. Then when you move it to the desktop screen (and drop it there) it should switch to highlighting the desktop's profile.
Does it do that?
Hi Catherine, sorry to hear about your woes.
Brian is much wiser than me at this stuff, but until he arrives, I'll throw in my two cents. I think you should do what the geek squad did - plug your computer into another screen. Any screen will do - do you have a television that would work, perhaps?
You can, don't worry. You just have to use the little "DisplayProfile" app that I explained in this article. (You don't even need the whole "TOGGLE.icc" business, just the app.)
Native is the starting point, that's all. If it proves not to be a sufficient match for your prints (as long as you're comparing in good light) then you will explore other options. This is all explained very clearly in my instructions.
Native is ideal if possible, because it means the least screwing around with the LUTs. The further we have to move from native, the greater the risk of banding.