File corruption in Aperture 2.1.4

recently I went back to work on photos I have opened many times. RAW CR2 format shot with canon 50D. The thumbnails look good but when I select one, it appears briefly in the large screen, but then I get a red screen with "unsupported image format". I exported as CR2 file and imported into lightroom and was OK. Aperture 1.5 was perfect and this version nothing but trouble. I get "black outs" when I try to adjust some images. After cropping and coming back to the photo later, it is uncropped. Just to mention a few problems.
Can you go back to 1.5??? What is going on??
Thanks for your help.

I had the same problem where photos were coming up with that **** red screen. Here's what someone suggested to me and it worked like a charm. Do a consistency check for Aperture. Launch Aperture while holding down the Command and Option keys until a window comes up with the option to do a consistency check or rebuild library. The consistency check will correct any issues with the permissions. Hope that helps.

Similar Messages

  • RAW files corrupted in Aperture

    With the upgrade to Mavricks and Aperture 3.5  I hoped my problems with RAW (ORF) images were over, but I am getting this again. Shooting RAW+JPEG and importing directly into Aperture, I'm seeing some image pairs like this:
    I've gone in and deleted the plist, cleaned up the Aperture Library, no luck. Any suggestions?
    Brian

    leoni et al,
    Seems there are two issues at work. One is the on-going problem with occasional RAW (ORF) images being corrupted. This post be a separate problem, e.g. using the Olympus in-camera "overlay" feature.
    In the OM-D I can take up to 3 RAW images and overlay them in the camera; in this case I used 2 files,  both are preserved and a new combined RAW image is recorded on the SD card.
    Adobe Camera RAW, and the native Olympus Viewer handle this with no problem, rendering both RAW images plus a combined RAW image. However, when imported into Aperture one of the 2 original RAW files disapears and the other RAW file is corrupted and a JPEG combined file is produced (as pictured above in the OP).
    Brian 

  • RAW files being corrupted by Aperture

    Some of my RAW files stored in Aperture come in clean but eventually show up as corrupt. Specifically, a rectangular portion of the image will become banded with colors that don't belong there.
    Sometimes I see this happen to a file just after some simple operation--say, adding a keyword. Whats' going on?
    Here's an example.
    http://lyonsimaging.smugmug.com/gallery/3547082

    Just to add my own recent image corruption problem. I was getting a pattern on some images, almost like heavy rain in vertical streaks. I thought it was an Aperture bug at first as it only appeared in Aperture. However, I could transfer images to other apps, and the fault had gone. The fault was only occurring when using the Highlight and Shadow tool.
    Thanks to a suggestion here, I finally found it was caused by my graphics card. I upgraded from my original Nvidia 5200FX 64MB, to a Radeon 9600XT 256MB. I was able to refit my old card, and the faulty was fixed. Turned out that the Radeon was overheating (these appear a lot in other forums, and an upgrade to the cooling is recommended). I have now refitted it with a Zalman copper cooler, and heat sinks to all the chips, and the problem seems to be cured.
    It does seem strange that yours are corrupted back to the master though.

  • Should I store my cr2 files in the aperture library?

    I have noticed aperture slowing, pausing and even crashing recently. I was wondering if storing too many cr2 files in the aperture library might cause this. At this time I have a little over 6000 cr2 files in the aperture library.

    Generally, no.  And generally, size alone is not a problem.
    I regularly run Libraries with 30,000 24 MPxl Images, both from the system drive or from external drives, and have no problems.
    I built up a Library of 1 MB JPG Images to 300,000 Images in order to test Aperture and did not encounter any problems except with Faces.
    Although I haven't tested it directly, my sense is that Aperture performs better with large Libraries when the Images' Masters are Referenced and located on a separate drive from the Library.  Put the Library on your highest-performing drive (almost always the system drive); put your Referenced Masters on a fast drive.
    The first things to check if Aperture begins to behave poorly are (off the top of my head):
    - drive space (Aperture needs a lot of free space on your system drive
    - other programs (Aperture is hardware intensive; a poorly written utility can slow the OS a little -- but that little can hobble Aperture on that machine)
    - Library corruption (Force-quitting can do this -- run "Repair")
    - File fragmentation (OS X does a good job preventing this, but I still recommend defragmenting large Libraries once a month.  Copying to a second drive, and then copying the copy back, defragments files.)
    - Also, make sure your copy of Aperture is up-to-date.

  • Large layered Photoshop files corrupted

    Is anyone out there using Mac G5 Quad Processor, working on large 500MB to 1.5MB layered Photoshop files (CS2) and not having any corruption to the files after opening and closing many times?

    I tested a file last night as follows:
    Sent file via 'Edit with Photoshop CS5' (as PSD 8-bit, sRGB color space) > changed background to normal layer > created circular selection around subject and inverted to remove most of image leaving transparent area (about 70% of image) > saved file > closed Photoshop > file updated in Aperture with black filling in the transparent area.
    Resent the PSD back to Photoshop (which opened correctly with transparent area) > created two new layers and sent one to background > filled new background layer with White and left top new layer transparent > saved again and closed Photoshop > file updated in Aperture with white showing in transparent areas (no black).
    AFAIK, this is how it is designed to work.
    My only other suggestion would be for you to create a new empty library (press Option while launching Aperture > Create New..) and then import one RAW or JPEG file and test.
    Note - you can reset Photoshop by holding down 'Command + Option + Shift' immediately after launching Photoshop and clicking 'Yes', then set the 'Maximize Compatibility...' to 'Always' again. Doing this prior to sending the file from new library would probably be best.
    Apologies in advance if you have already tried this and for outlining procedures that you are already familiar with (just not sure what level Photoshop user you are).

  • Is there a cure for persistent file corruptions across the suite?

    i am having terrible and consistent problems with file corruptions across the suite. for example…
    1: i collected for output (indesign) – corrupted over 100 small images that were linked.
    2: opened an indesign job and all linked files failed to update and could not be imported (simply would not import those files and were all corrupted).
    3: had a hang in photoshop followed by a 150:30 error (would not open any of my applications). this prompted a clean install of system and adobe cs4 see below
    4: most recently, had a hang in photoshop (photoshop will also no "force quit") whilst indesign was open. two of my image files corrupted and, most surprisingly, all my illustrator files that i had placed also corrupted (will not even open in illustrator any more). illustrator was not even running at the time, so, get this – a hang in photoshop destroys illustrator files simply because they are placed in indesign.
    this last event has made me more certain than ever that there is a fundamental problem at the cs4 core.
    can anyone help?
    please note the following:
    i am running a macintosh imac, 2.66 GHz Intel Core 2 Duo (latest imac), with 4 GB 1067 MHz DDR3 ram.
    before this last disaster, i had reloaded the system software (archive and install), and updated it all the way to version 10.5.8
    i then uninstalled the creative suite, ran the cleanscript from adobe, reloaded the creative suite, downloaded all the cs4 updates
    (so, latest mac, latest system, latest cs4 – all clean installs).
    is there something i can do? or is this just a very unstable and disappointing upgrade – i have had nothing but problems from day one!
    many thanks if anyone has any advice.

    Re: 150:30 error:
    Please try this KB article's solutions, and report back on how it went for you. If you can provide details about any recent OS updates, backups, or migrations, that would help is nail down the root cause of the new rash of this error for Mac users recently:
    http://kb2.adobe.com/cps/512/cpsid_51260.html

  • Downlaoded .exe for Firefox5 gives "file corrupted" error when I try to open it

    I am running Windows XP on Parallels 5 on top of MAC OSX on an iMac24.
    I have no problems downloading Firefox 5 on OSX for Mac, nor for downloading Thunderbird on WinXP/Parallels5.
    Just Firefox5.exe comes up "file corrupted" when I try to run it or open it on WinXP/Parallels5.

    Post in Microsoft's Powerpoint (Mac) message boards.

  • Sync File Corruption with 64-bit Vista/iTunes

    I'm getting some file corruption problems when trying to sync my new 16GB iPhone with the latest 64-bit iTunes (7.6.0.29). "yes I have the 64-bit version".
    The sync seems to go correctly, but I have yet to be able to play any videos all the way through. Videos purchased from iTunes as well as self encoded files. All said files were working on my 60GB iPod Video with previous versions of iTunes on the same 64-bit Vista machine.
    The videos will start playing fine, but will eventually reach a point in the file that was corrupted during transfer, the audio will drop out and the video will distort, then it exits from the video as if it reached the end of the file. No error messages or anything. If I play the file again, it will do the same thing at the exact same spot, so its a problem in the file. Now, if I remove the file and add it back, the file still has the same problem, but in a different location, which means the source is fine, but the copy to the device during the sync is the issue.
    To test, I synced the exact same content from my notebook which is 32-bit XP, and zero problems. So I'm currently just using my notebook for syncing at the moment.
    Anyone else with 64-bit Vista have a similar issue?

    Hello
    I have a couple troubleshooting steps I would like you to try. I myself do not have a 64 bit Vista so I can not test this to confirm if the same issue occurs or not.
    1. Attempt to Sync content using each of the USB Ports. See if all USB Ports pose the same issue with the video. Or if you found when where it does not occur.
    2. Test on a new user on the Vista Machine. If possible take at least one or 2 movies and copy them onto a flash drive or something. And bring them into iTunes on a new user account. You may need to Authorize that user and De-authorize when your done. Does the same issue occur?
    3. If you perform a reboot on the iPhone, Then Sync Data over. Does the same issue occur?
    4. If possible could you restore the iPhone. Then Re-sync and see if same issue occurs.
    5. Is this happening with all videos? or only certain ones? Does the corruption occur at the same time frame every time? If so is it the same time frame for all videos or slightly different?
    6. Perform an Uninstall and Reinstall of iTunes on your system, See if same issue occurs.
    Let us know how it goes.

  • Convert RAW Files in Your Aperture Database to Adobe DNG Files

    The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files.  In the example below I am assuming that your Aperture Library has ARW and CR2 files.  These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library).  The steps are:
    1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu.  From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
    2. Drag the "Masters" folder out of the Package and place it on your Desktop.  The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
    3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
    4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files.  Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc.  In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
    5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above).  The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above.  Do NOT put the .DNG files in your search criteria.  Select all the files found in the search and move them to the Trash.  This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
    6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
    7. Select the Finder Window containing the Aperture Library Package Contents.
    8. If there is a file called "ApertureData.xml" then open it with a text editor.  Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search).  Make sure you cover all the file types incorporated in your particular system.  Save the "ApertureData.xml" file.
    9. Traverse to the Database/apdb directory.  Select the "BigBlobs.apdb" file and open it with a Hex editor.  In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/).  Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex.  In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window.  In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search).  Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
    10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
    That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files.  Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish.  This process works because:
    1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
    2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
    Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source.  Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source.  In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.

    A rather involved method, David.
    I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
    And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
    I convert selected raw files this way - without manually patching the Aperture Library:
    Export the originals of the raw images that I want to convert.
    Run dng-converter.
    Import the converted originals back, flag them,  and move them to the project they came from.
    Sort the project by capture date, so that identical images are show side by side.
    Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
    It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
    Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
    Regards
    Léonie

  • Transaction log shipping restore with standby failed: log file corrupted

    Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
    Date                     
    9/10/2014 6:09:27 AM
    Log                        
    Job History (LSRestore_DATA_TPSSYS)
    Step ID                
    1
    Server                  
    DATADR
    Job Name                           
    LSRestore_DATA_TPSSYS
    Step Name                        
    Log shipping restore log job step.
    Duration                             
    00:00:03
    Sql Severity        0
    Sql Message ID 0
    Operator Emailed           
    Operator Net sent          
    Operator Paged               
    Retries Attempted         
    0
    Message
    2014-09-10 06:09:30.37  *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred while processing the log for database 'TPSSYS'. 
    If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
    Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Deleting old log backup files. Primary Database: 'TPSSYS'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.38  ----- END OF TRANSACTION LOG RESTORE    
    Exit Status: 1 (Error)

    I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in  that server with log shipping configuration
    error :
    Message
    2014-09-12 10:50:03.18    *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-12 10:50:03.18    *** Error: An error occurred while processing the log for database 'EAPDAT'.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
    Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
    As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
    Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
    Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • "FILE CORRUPTED" error message on N 78

    My phone is a Nokia N78 and my problem is as followed:
    Before updating the firmware from version 12 to version 20, I had google maps installed. After updating over the air, google maps (and also several other apps) got removed. When i tried to download and install google maps again and tried to install it again, it keeps saying "file corrupted". The same goes with other apps i try to download and install. But I have no trouble installing java apps.
    I am wondering if anyone knows how to solve this problem?
    Solved!
    Go to Solution.

    you are very welcome i am so glad that you got your issues sorted. i know how frustrating it can be to have a phone and potentially no 'way out'. been there and done that, that is why i joined this forum i wanted to learn more and find more answers to some questions. technology in general can be frustrating and its ever changing so we have to keep up or we will drown in frustration be well, rad.
    ps. and you are correct, i am no expert, my solution is not expert either more of a been down this road solution. i am just another user on this forum that sometimes gets the right answer
    Message Edited by radical24 on 19-Jan-2009 07:54 PM
    You know what I love about you the most, the fact that you are not me ! In love with technology and all that it can offer. Join me in discovery....

  • File corruption on SDCard when multiple files are being written from WinCE 6.0R3

    We currently have file corruption problems which we have been able to reproduce on our system which uses WinCE 6.0R3. We have an SDCard in our system which is mounted as the root FS.  When multiple files are being written to the file system we occasionally
    see file corruption with data destined from one file, ending up in another file, or in another location in the same file.  We have already written test SW that we have been able to use to reproduce the problem, and have worked with the SDCard vendor to
    check that the memory controller on the card is not the source of the problems.
    We know that the data we send to WriteFile() is correct, and that the data which eventually gets sent through the SDCard driver to the SD card is already corrupted.
    We believe that the problem is somewhere in the microsoft private sources between the high level filesystem API calls and the low level device calls that get the data onto the HW.
    We have confirmed that the cards that get corrupted are all good and this is not a case ofpoor quality flash memory in the cards. The same cards that fail under WinCE 6.0R3 never fail under the same types of testing on Windows, Mac OX, or linux.  We
    can hammer the cards with single files writes over and over, but as soon as multiple threads are writing multiple files it is only a matter of time before a corruption occurs.
    One of the big problems is that we are using the sqlcompact DB for storing some data and this DB uses a cache which get's flushed on it's own schedule. Often the DB gets corrupted because other files are being written when the DB decides to flush.
    So we can reproduce the error (with enough time), and we know that data into the windows CE stack of code is good, but it comes out to the SDcard driver corrupted.  We have tried to minimize writes to the file system, but so far we have not found a
    way to make sure only one file can be written at once. Is there a setting or an API call that we can make to force the OS into only allowing one file write at a time, or a way of seeing how the multiple files are managed in the private sources?
    Thanks
    Peter

    All QFE's have been applied we are building the image so we have some control.
    I have build an image which used the debug DLL's of the FATFS and I have enabled all of the DebugZones.  The problem is still happening. From the timings in the debug logs and the timestamps in the data which corrupts the test file I have been able
    to see that the file is corrupted AFTER the write is complete. Or at least that's how it seems.
    We finished writing the file and closed the handle. Then more data is written to other files. When we get around to verifying the file it now contains data from the files that were subsequently written.
    What I think I need to do is figure out in detail how the two files were "laid down" onto the SDCard.  If the system used the same cluster to write the 2 files then that would explain the issue.

  • H8-1520t: sfc /scannow reported file corruption in Windows 8.1

    My computer (h8-1520t) computer had had file corruption error reported by sfc /scannow.
    The corruption was rather common corruption as discovered elsewhere on the internet.  The corruption pertained to prncacla.inf and it was repaired only by using DISM.exe /Online /Cleanup-image /Restorehealth.  The corruption occured while the computer was doing automatic maintenance which locked up my system.  After forcing a shutdown and rebooting, I immediately ran sfc /scannow and that's when the corruption was first detected.
    Now sfc /scannow finds no corruption and automatic maintence runs to completion.
    Since this is a rather common corruption error and there's no explanation as to what causes the problem, should I send my computer, which it's still under warranty, back to HP ---or--- did I corrected the corruption properly ? ? ?
    On additional question: What on earth causes that common corruption to occur anyway.
    Also: UEFI diagnostics extensively run and the extensive testing revealed no problems with system board, hard drive, memory, processor (i7-3770), graphics card memory (Radeon HD 8570).
    If I should be concerned about my computer being a dud and lemon, I'd like to know... Or, did I fix the corruption correctly?
    Thanks,
    Mark

    Hi Mark,
    You may want to review this article.
    If you are not comfortable with the Windows repair process then you can use the external HP recovery media to reload you PC back to a day one factory fresh condition.  Backup your data before doing so.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • File Corruption During Sync Windows 8.1

    Hi
    I have recently introduced some Windows 8.1 systems into our environment, a Sony laptop and a non branded custom build, both systems are running Windows 8.1 Pro.
    Our environment is as follows:
    Windows Server 2008 domain
    PPTP VPN for laptop users using a Watchguard X515.
    Netgear ReadyNAS 2100 for Network Folders.
    Folder redirection in place for Documents and Desktop.
    Offline files in use. Users have the ability to make shared network files available offline if required.
    The first device we had with 8.1 Pro was a Sony laptop for our Marketing Director.  He has manually made a few shared network folders available offline for when he is out of the office and unable to connect to the VPN.  
    We first noticed an issue a few weeks ago when he came to me telling me that one of his documents were corrupt.  The file was one of the ones he has made available offline.  When he got into the office he ran a manual sync, to put the updates onto
    our shared drive.  When he next came to open it, the file was corrupt with the following message:
    'Excel cannot open the file 'XXXX XXXX.xlsx' because the file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file'.
    I ran the file through Excel's file repair, which couldn't fix the problem and I tried a few software packages from the internet which said the file was unrecoverable, to no avail.  We tried to recreate the issue but couldn't so we put it down to a one
    off.  A few days later, it happened again under the same circumstances.
    I put it down to something happening while the laptop was offline, however whilst researching this, the same problem happened on a Windows 8.1 Pro Desktop.  This system never leaves the office, which led to some confusion.
    Everywhere I look points to ransomware, however I have run full scans with Sophos and Malwarebytes, and both come back clean, and the issue is only occurring on 8.1 Pro systems, 7 Pro and 8 Pro systems are fine.
    The user with the 8.1 Pro desktop created a test spreadsheet for me, and this morning we managed to recreate the problem.  When running a manual sync, the Offline Files comes back with an error, stating that the network copy has been deleted, would you
    like to copy the local copy or delete it?  When we copy the local copy to the network, and then try to open it, we get the previous error about file corruption.
    Any help would be greatly appreciated as I will have to roll the systems back to Windows 7 if I cant get it resolved, which would be a shame as the laptop is has a flip screen to turn it into a tablet.
    Cheers
    Jim

    Hi,
    You can boot the problematic system with clean boot to check if there is any third party software conflicts.
    Steps to clean boot: 
    1. Click Start->Run...-> type msconfig and press Enter
    2. Click Services tab and select Hide All Microsoft Services and Disable All third party Services.
    3. Click Startup tab and Disable All startup items
    4. Click OK and choose Restart
    5. After reboot, check whether the problem still occurs
    In additional, please refer to the thread below to troubleshoot the issue:
    ms excel problem
    http://social.technet.microsoft.com/Forums/office/en-US/fc38d024-c767-4b9d-9ba8-60422240f579/ms-excel-problem?forum=officesetupdeployprevious
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • I reinstalled my system on a new hard drive, from time machine. However my old photos seem corrupt within aperture. iphoto seems okay.  Have you heard of this?

    I reinstalled my system on a new hard drive, from time machine. However my old photos seem corrupt within aperture. iphoto seems okay. New photos take a long time to load as well.
    Have you heard of this?
    Thanks

    We need a little more information to be able to help.
    However my old photos seem corrupt within aperture.
    What kind of corruption? And when do you see it? All your images, or only some? Are the images distorted, discolored, or not displayed at all?
    Are you shooting in raw? Is your library referenced or managed? Is your library on your system volume or on an external harddrive?
    And it would help to know your MacOS version and Aperture version too.
    Regards
    Léonie

Maybe you are looking for