Problem Parsing the JPEG Data??

well well well. the first time, using the Windows rotate trick worked for me. Now it's not working. I'm just lost... These files aren't any newer, in fact they are from the same bunch as before. I mass rotated them and back. didn't work. I rotated one and back. didn't work. I even rotated it just once, to see if maybe Windows is simply undoing the rotate when I go CCW after CW... still didn't work... at least on the one image that I'm trying. So this isn't a very solid solution then.

just lost. I don't want to save the file in another format. that's ridiculous, even if saving to lossless TIF, it's still ridiculous... when it's "clearly" (?) the header data... something is wonky anyway. It's within the the technical requirements of JPEG, but something is non-standard. Opening as RAW is also a terrible workaround because it majorly interrupts the workflow, and can't easily be batched.

This happens a lot with images Dloaded from Facebook as well. Think some of these images contain extra data that throws PS off.

it's a metadata issue. in the jpeg header. The solution posted saying to rotate + un-rotate in Windows Explorer works perfectly... without LOSS due to COMPRESSING/TRANSCODING the file in mspaint or whatever. It's also far easier than opening then saving in another program, because you can select multiple files in Windows Explorer, right-click and rotate all at once.

I opened the rotated file and a copy of the original in a text comparison program (WinMerge), and the only part of the file changed is the very top section (the header). the actual jpeg data is left untouched. funny that even though the rotate function is solely intended to change/set the "orientation" tag in the EXIF data, the entire header is essentially replaced altogether... I'm assuming because it's invalid data anyway, Windows just (re)creates the EXIF header according to spec. (Instagram photos don't even have EXIF data to begin with. Just and IPTC tag with some strange "special instructions" characters). As to what the header actually is... well who knows? It's obviously a junked header. Still a valid jpeg, but Photoshop seems to be especially fussy.

rotating & un-rotating a file without EXIF.orientation leaves the orientation set to "Top left", which is the default location for the first pixel in a jpeg anyway.

For curiosity's sake, I really do wonder what the MEANING of Instagram's junk header is... maybe it really is that simple, as mentioned here before... that they found a dirty trick to prevent people from shooping their goods.

I used Photoshop Elements 2015 last year to edit some pictures that I had scanned from photographs of my ancestors.  I didn't have any problems with loading any of them into Photoshop.  I just got back to doing this work and now I find all kinds of problems as users have mentioned here.  I decided to upgrade to Photoshop Elements 2018 thinking that would solve the problem but it hasn't.  The problem is still the same plus a lot of new errors.  It seems that I have upgraded for nothing.

I did use the Microsoft Paint workaround and it worked.  I am disappointed that people have been mentioning this problem since 2015 and here it is 2018 and the problem still exists.  I cannot understand why I didn't have this problem last year.  I wonder if the various upgrades to the Microsoft Operating System (I'm running 10) could have something to do with it.

There is an easier way for mac. Just open the file with the native Preview app, choose File>Export, select PNG and save.
No need to import on Photos app.

The link below will fix the following issues:

• "Could not complete your request because of a problem parsing the JPEG data"
• "Could not complete your request because there is not enough memory (RAM)"
• "There was an error opening your printer. Printing functions will not be available until you have selected a printer & reopened any document"

Error: An integer between 50 and 8 is required | Elements | Windows 10

Just had this 'Parsing JPEG Data' problem in PSE 2018. I have a strong suspicion that for me it is brought on by a Memory (RAM) issue with PS which is reported elsewhere and could in fact be the root of the problem that johns9184832​ reported. I got the 'Parsing' message when I tried to open more than 4 images in PSE simultaneously.

I found this forum post:

Problem with available RAM

Which linked to a workround here:

Error while accessing performance preferences - 'An integer between 96 and 8 is required.'

The workround solution in that last page worked for me - the 'Parsing JPEG Data' problem stopped and I was able to make PSE run faster! Note that Adobe still need to fix the memory usage problem properly though.

Just want top throw in my two cents for nj.arora​ .

Noticed people here are saying they have problems with JPEGs downloaded from instagram.

I'm having the same issue when I try to load JPEGs downloaded from facebook.

Considering that these two websites are owned by the same company, I would assume that it has something to do with their compression algorithms, or maybe just some facebook-specific metadata which Photoshop does not yet know how to parse.

Facebook is notorious for its crappy file compression and I wouldn't be surprised to hear that Instagram follows the same practices. It stands to reason that a fix by clipping and saving to a new file just removes whatever data Facebook attaches that is not part of a standard JPEG.

I found a way to do this. Go to this website JPG a PNG – Convierta de JPG a PNG  place your image and converted into PNG than go to psd and place it.

Regedit (admin) -> HKEY_CURRENT_USER -> Software -> Adobe -> Photoshop -> 110.0 or 120.0 -> create DWORD 32bit -> name: 'OverridePhysicalMemoryMB', value: (for example) 4096 -> OK -> run Photoshop. Have a nice day.