“Error 0x80070057: The parameter is incorrect” when editing JPEG metadata












1















When trying to change the metadata on the NYT1 2014 MU69 image taken by New Horizons image that I downloaded from a blog post, I get this error:




An unexpected error is keeping you from appying properties to the file. If you continue to receive this error, you can use the error code to search for help with this problem.



Error 0x80070057: The parameter is incorrect.




Screenshot:



Screenshot of Error 0x80070057 on Windows 10



Some observations:




  • The path of the file location is nowhere near 256 characters long

  • The file name is not any of the Windows reserved names

  • The file is not read-only, and I have full read/write permissions for the file.

  • Even if I re-download the image or rename the image, the error still reliably appears every time.

  • I can still edit the metadata on other JPEG files in the same folder just fine, so I don't think this is related to system or hard drive corruption.

  • If I push "Skip", the action completes, but then no metadata is changed.


Possibly related threads that I already looked at:




  • Error 0x80070057 when editing JPG metadata through explorer

  • Error 0x80070057 when adding photo tags in Pictures folder

  • Error 0x80070057 when attempting to change image metadata shown at the bottom of explorer

  • Error 0x80070057 when copying images from iPhone 5s to Windows 8.1

  • Error 0x80070057 when deleting Autorun.inf.mal folder










share|improve this question





























    1















    When trying to change the metadata on the NYT1 2014 MU69 image taken by New Horizons image that I downloaded from a blog post, I get this error:




    An unexpected error is keeping you from appying properties to the file. If you continue to receive this error, you can use the error code to search for help with this problem.



    Error 0x80070057: The parameter is incorrect.




    Screenshot:



    Screenshot of Error 0x80070057 on Windows 10



    Some observations:




    • The path of the file location is nowhere near 256 characters long

    • The file name is not any of the Windows reserved names

    • The file is not read-only, and I have full read/write permissions for the file.

    • Even if I re-download the image or rename the image, the error still reliably appears every time.

    • I can still edit the metadata on other JPEG files in the same folder just fine, so I don't think this is related to system or hard drive corruption.

    • If I push "Skip", the action completes, but then no metadata is changed.


    Possibly related threads that I already looked at:




    • Error 0x80070057 when editing JPG metadata through explorer

    • Error 0x80070057 when adding photo tags in Pictures folder

    • Error 0x80070057 when attempting to change image metadata shown at the bottom of explorer

    • Error 0x80070057 when copying images from iPhone 5s to Windows 8.1

    • Error 0x80070057 when deleting Autorun.inf.mal folder










    share|improve this question



























      1












      1








      1








      When trying to change the metadata on the NYT1 2014 MU69 image taken by New Horizons image that I downloaded from a blog post, I get this error:




      An unexpected error is keeping you from appying properties to the file. If you continue to receive this error, you can use the error code to search for help with this problem.



      Error 0x80070057: The parameter is incorrect.




      Screenshot:



      Screenshot of Error 0x80070057 on Windows 10



      Some observations:




      • The path of the file location is nowhere near 256 characters long

      • The file name is not any of the Windows reserved names

      • The file is not read-only, and I have full read/write permissions for the file.

      • Even if I re-download the image or rename the image, the error still reliably appears every time.

      • I can still edit the metadata on other JPEG files in the same folder just fine, so I don't think this is related to system or hard drive corruption.

      • If I push "Skip", the action completes, but then no metadata is changed.


      Possibly related threads that I already looked at:




      • Error 0x80070057 when editing JPG metadata through explorer

      • Error 0x80070057 when adding photo tags in Pictures folder

      • Error 0x80070057 when attempting to change image metadata shown at the bottom of explorer

      • Error 0x80070057 when copying images from iPhone 5s to Windows 8.1

      • Error 0x80070057 when deleting Autorun.inf.mal folder










      share|improve this question
















      When trying to change the metadata on the NYT1 2014 MU69 image taken by New Horizons image that I downloaded from a blog post, I get this error:




      An unexpected error is keeping you from appying properties to the file. If you continue to receive this error, you can use the error code to search for help with this problem.



      Error 0x80070057: The parameter is incorrect.




      Screenshot:



      Screenshot of Error 0x80070057 on Windows 10



      Some observations:




      • The path of the file location is nowhere near 256 characters long

      • The file name is not any of the Windows reserved names

      • The file is not read-only, and I have full read/write permissions for the file.

      • Even if I re-download the image or rename the image, the error still reliably appears every time.

      • I can still edit the metadata on other JPEG files in the same folder just fine, so I don't think this is related to system or hard drive corruption.

      • If I push "Skip", the action completes, but then no metadata is changed.


      Possibly related threads that I already looked at:




      • Error 0x80070057 when editing JPG metadata through explorer

      • Error 0x80070057 when adding photo tags in Pictures folder

      • Error 0x80070057 when attempting to change image metadata shown at the bottom of explorer

      • Error 0x80070057 when copying images from iPhone 5s to Windows 8.1

      • Error 0x80070057 when deleting Autorun.inf.mal folder







      windows windows-10 windows-explorer metadata exif






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 2 at 22:33







      ahiijny

















      asked Jan 2 at 22:25









      ahiijnyahiijny

      1867




      1867






















          1 Answer
          1






          active

          oldest

          votes


















          1














          I don't know the root cause of this error, but it seems to have something to do with the file itself. Using exiftool to repair corrupted EXIF seems to fix the problem. The command looks like this:



          exiftool -all= -tagsfromfile @ -all:all -unsafe -icc_profile bad.jpg


          More detail on what this does:




          This command deletes all metadata then copies all writable tags that can be extracted from the original image to the same locations in the updated image. The "Unsafe" tag is a shortcut for unsafe EXIF tags in JPEG images which are not normally copied. JPEG images may also contain an ICC color profile which should be preserved. The "ICC_Profile" tag is also marked as unsafe, but is not part of the EXIF so it isn't covered by the "Unsafe" shortcut and must be specified separately.



          Note: ExifTool will not modify the JPEG image data.



          Advanced: The byte order of the newly created EXIF is set by the value of the ExifByteOrder tag. If ExifByteOrder is not set then the byte order is determined by the ordering of the MakerNotes if they are copied, otherwise big-endian ("MM") byte order is used by default. ExifByteOrder may be set to a specific value to force a particular byte order when creating new EXIF (eg. "-ExifByteOrder=II" for little-endian).




          Note also that running the above command on a file named bad.jpg will preserve a copy of the original file under the filename bad.jpg_original.






          share|improve this answer


























          • I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

            – StarGeek
            Jan 3 at 0:16











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389971%2ferror-0x80070057-the-parameter-is-incorrect-when-editing-jpeg-metadata%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          I don't know the root cause of this error, but it seems to have something to do with the file itself. Using exiftool to repair corrupted EXIF seems to fix the problem. The command looks like this:



          exiftool -all= -tagsfromfile @ -all:all -unsafe -icc_profile bad.jpg


          More detail on what this does:




          This command deletes all metadata then copies all writable tags that can be extracted from the original image to the same locations in the updated image. The "Unsafe" tag is a shortcut for unsafe EXIF tags in JPEG images which are not normally copied. JPEG images may also contain an ICC color profile which should be preserved. The "ICC_Profile" tag is also marked as unsafe, but is not part of the EXIF so it isn't covered by the "Unsafe" shortcut and must be specified separately.



          Note: ExifTool will not modify the JPEG image data.



          Advanced: The byte order of the newly created EXIF is set by the value of the ExifByteOrder tag. If ExifByteOrder is not set then the byte order is determined by the ordering of the MakerNotes if they are copied, otherwise big-endian ("MM") byte order is used by default. ExifByteOrder may be set to a specific value to force a particular byte order when creating new EXIF (eg. "-ExifByteOrder=II" for little-endian).




          Note also that running the above command on a file named bad.jpg will preserve a copy of the original file under the filename bad.jpg_original.






          share|improve this answer


























          • I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

            – StarGeek
            Jan 3 at 0:16
















          1














          I don't know the root cause of this error, but it seems to have something to do with the file itself. Using exiftool to repair corrupted EXIF seems to fix the problem. The command looks like this:



          exiftool -all= -tagsfromfile @ -all:all -unsafe -icc_profile bad.jpg


          More detail on what this does:




          This command deletes all metadata then copies all writable tags that can be extracted from the original image to the same locations in the updated image. The "Unsafe" tag is a shortcut for unsafe EXIF tags in JPEG images which are not normally copied. JPEG images may also contain an ICC color profile which should be preserved. The "ICC_Profile" tag is also marked as unsafe, but is not part of the EXIF so it isn't covered by the "Unsafe" shortcut and must be specified separately.



          Note: ExifTool will not modify the JPEG image data.



          Advanced: The byte order of the newly created EXIF is set by the value of the ExifByteOrder tag. If ExifByteOrder is not set then the byte order is determined by the ordering of the MakerNotes if they are copied, otherwise big-endian ("MM") byte order is used by default. ExifByteOrder may be set to a specific value to force a particular byte order when creating new EXIF (eg. "-ExifByteOrder=II" for little-endian).




          Note also that running the above command on a file named bad.jpg will preserve a copy of the original file under the filename bad.jpg_original.






          share|improve this answer


























          • I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

            – StarGeek
            Jan 3 at 0:16














          1












          1








          1







          I don't know the root cause of this error, but it seems to have something to do with the file itself. Using exiftool to repair corrupted EXIF seems to fix the problem. The command looks like this:



          exiftool -all= -tagsfromfile @ -all:all -unsafe -icc_profile bad.jpg


          More detail on what this does:




          This command deletes all metadata then copies all writable tags that can be extracted from the original image to the same locations in the updated image. The "Unsafe" tag is a shortcut for unsafe EXIF tags in JPEG images which are not normally copied. JPEG images may also contain an ICC color profile which should be preserved. The "ICC_Profile" tag is also marked as unsafe, but is not part of the EXIF so it isn't covered by the "Unsafe" shortcut and must be specified separately.



          Note: ExifTool will not modify the JPEG image data.



          Advanced: The byte order of the newly created EXIF is set by the value of the ExifByteOrder tag. If ExifByteOrder is not set then the byte order is determined by the ordering of the MakerNotes if they are copied, otherwise big-endian ("MM") byte order is used by default. ExifByteOrder may be set to a specific value to force a particular byte order when creating new EXIF (eg. "-ExifByteOrder=II" for little-endian).




          Note also that running the above command on a file named bad.jpg will preserve a copy of the original file under the filename bad.jpg_original.






          share|improve this answer















          I don't know the root cause of this error, but it seems to have something to do with the file itself. Using exiftool to repair corrupted EXIF seems to fix the problem. The command looks like this:



          exiftool -all= -tagsfromfile @ -all:all -unsafe -icc_profile bad.jpg


          More detail on what this does:




          This command deletes all metadata then copies all writable tags that can be extracted from the original image to the same locations in the updated image. The "Unsafe" tag is a shortcut for unsafe EXIF tags in JPEG images which are not normally copied. JPEG images may also contain an ICC color profile which should be preserved. The "ICC_Profile" tag is also marked as unsafe, but is not part of the EXIF so it isn't covered by the "Unsafe" shortcut and must be specified separately.



          Note: ExifTool will not modify the JPEG image data.



          Advanced: The byte order of the newly created EXIF is set by the value of the ExifByteOrder tag. If ExifByteOrder is not set then the byte order is determined by the ordering of the MakerNotes if they are copied, otherwise big-endian ("MM") byte order is used by default. ExifByteOrder may be set to a specific value to force a particular byte order when creating new EXIF (eg. "-ExifByteOrder=II" for little-endian).




          Note also that running the above command on a file named bad.jpg will preserve a copy of the original file under the filename bad.jpg_original.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 2 at 22:43

























          answered Jan 2 at 22:25









          ahiijnyahiijny

          1867




          1867













          • I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

            – StarGeek
            Jan 3 at 0:16



















          • I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

            – StarGeek
            Jan 3 at 0:16

















          I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

          – StarGeek
          Jan 3 at 0:16





          I would suspect there is a problem with the XMP data embedded in that image, as there isn't an EXIF block in there. Using exiftool to make a simple alteration, such as exiftool "-subject+=test keyword" 20190102_mu69_nyt1_f840.jpg and then editing with Windows seems to remove the problem.

          – StarGeek
          Jan 3 at 0:16


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389971%2ferror-0x80070057-the-parameter-is-incorrect-when-editing-jpeg-metadata%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Probability when a professor distributes a quiz and homework assignment to a class of n students.

          Aardman Animations

          Are they similar matrix