FileVault decryption problem fixed

I had posted on April 30 that I could not decrypt my FileVault home folder. TechToolPro 4 and Disk Utility both reported problems, but offered no solutions. Today I got a DiskWarrior CD, and it immediately found the problems and fixed them. Easy as pie. Wanted to post this in case others have similar issues with FileVault.

Well done, and thanks for the post back.

Similar Messages

  • Does  Mavericks have the problem fixed with working with the Dell UltraSharp U3014 30 inch monitor?

    Does  Mavericks have the problem fixed with working with the Dell UltraSharp U3014 30 inch monitor?

    I have this (or a similar) issue and I did notice something interesting. After I boot into Windows via Bootcamp (where I have the U3014 specfic driver installed) and then reboot into MacOS X (Mavericks) the monitor works flawlessly.
    I would hazard a guess that this means bootcamp is retaining the driver used in Windows. Kind of the reverse of the TB GBE adapter driver issue.
    To explain my issue for anyone else: the monitor flicks on and off as if the connection was poor. Connecting via HDMI. Connection is fine and as stated, everything works fine in Bootcamp.

  • I have problem " verify your emal "   i can't change account , i removed application and instell again , same problem fix email and " verify email"

    i have problem " verify your emal "   i can't change account , i removed application and instell again , same problem fix email and " verify email"

    The Email ID provided here has CC registered to it in active status. The Email also stands verified. Are you using any other Email ID ?
    Let me know if you are facing issue regarding verification by activating the Cc with the email ID provided here.
    Regards
    Rajshree

  • HT3552 I am billed 3 times for a same item. How can I get the problem fixed? Thanks a lot for your help.

    I am billed 3 times for a same item. How can I get the problem fixed? Thanks a lot for yur help. nhuttan448

    Go here:
    http://www.apple.com/support/itunes/contact/
    and follow the instructions to report the issue to the iTunes Store.
    Regards.

  • Jumpy scrowl control with mouse.Only with Firefox, not Internet explorer. Problem fixed when I updated to 6. 0.2 but problems returned after about a week.. 0.2

    Jumpy scroll wheel control with mouse. Only with Firefox, not Internet explorer.Even pushing the scroll wheel and trying to adjust for a smooth easy scroll the text stops and starts. Problem fixed itself when I updated to 6. 0.2 from an older version but the problem returned after about a week.. The problems go away when I go to web site and scroll but is back when I return to my home page (mozilla firefox)

    Good post, and glad to hear you had a solid transition. Mine went well too, though I think I beat the rush.
    It's worth noting that the vast and overwhelming majority of headaches people were experiencing were related to download and activation servers (as well as credit check servers for some mobile carriers) being crushed and overwhelmed.
    To give you an idea of just how crushed, here are some numbers. In the last year, something in the neighborhood of 8 million iPhones have been sold. That's just shy of 22,000 per day. So the typical traffic is around 22,000 times a day, someone is hitting the server for update/activation.
    This weekend, Apple sold 1 million iPhones. In other words, 333,333 phones per day. Holy crap!
    As if that wasn't enough, there are 8 million of us out there with the first generation iPhone. Not only do we need to download the new firmware, but we have to install it. The installation process requires hitting the activation server again, to validate the phone. Mind you, not everybody upgraded this weekend, but a few million did. For the sake of argument, we'll assume that's 1 million a day. So, instead of the normall traffic of 22K phones a day, those activation servers got SLAMMED with 1.33 million activations per day.
    It ***** that some people had delays and hiccups and a hard time and everything, but completely understandable. With luck things will run more smoothly from here on out.
    Trilo

  • Filevault decrypt failure

    My usual backup method requires turning off Filevault. However, when trying to do so I get the error: *"an error occurred: an error occurred during decryption (an error occurred during copying). Filevault will be turned on for this home folder and the home folder will still be encrypted"*. I ran disk utility verify disk and repair disk permissions to no avail. I still get the error.
    I am running 10.4.10, 2gRAM, 2.33 IC2D MBP.
    Help?

    Perhaps one of the following will help:
    http://docs.info.apple.com/article.html?artnum=303617
    http://docs.info.apple.com/article.html?artnum=303617
    http://www.macosxhints.com/article.php?story=20050326041757989
    Solving File Vault Related Problems
    Syd Low offered a helpful tip about recoving damaged Mac OS X FileVault data:
    Apple's knowledge base article on this problem - How to verify or repair a home directory image - didn't work for me. When you click repair at step 12 Disk Utilty will not be able to repair the volume because of permission problems. Here's what I did:
    I added write permission using the command line. Open the Terminal (Utilities folder) and at the prompt enter the following commands pressing return at the end of each:
    prompt > cd /Users/accountname
    prompt > sudo chmod g+w accountname.sparseimage
    You will be asked to enter your admin password. It will not be echoed.
    prompt > sudo chmod g+w /Users/accountname
    Now you can run Disk Utility to repair the image successfully. Remember to change the permissions back afterwards:
    prompt > sudo chmod g-w accountname.sparseimage
    prompt > sudo chmod g-w /Users/accountname
    Also read the following in the event the above doesn't help:
    FileVault-protected Home shows less capacity than what's available on the hard disk.
    Some possible fixes if FileVault goes awry.

  • Starting up from installation disk/filevault 2 problems

    I'm trying to get filevault 2 going on Lion. When I do I get an error message telling me I need to reformat my disk and reinstall Lion. I have tried running disk repair, that has identified I have a problem with my disk being corrupted. Disk repair has instructed my to reboot with an installation disk in order to repair it. However, I have installed Lion already and am therefore unable to create an installation disk. I have also tried a number of times restarting using "command-R", but this does not work either. I've also tried using a Snow Lepoard installation disk, which didn't work.I was previously using PGP encryption with Snow Leopard, I'm not sure if this is relevant, but I decrypted my hard disk and uninstalled it before upgrading.
    Any help or advice would be much appreciated!

    What happens is this: the apple logo appears, the daisy wheel spins, but then the screen goes blank. There is a lot of whirring from the innards, but eventually this all goes quite (Im still holding down the 'c' key). Then nothing. Ive waited up to 10 mins for some signs of life, but no joy.
    First, I'd expect booting from the installation disk to take a long time.
    I don't agree. I have never seen it take nearly as long as described above, nor had the screen go black for ten minutes. When I boot from the Mac OS X install disk on any of my Macs, it takes maybe a couple minutes. Longer than when booting from a hard drive, yes, but 10 minutes is not reasonable.
    Based on the description above, I would guess that either the install disk is bad or the hardware is bad. Either way, a trip to the Genius Bar would probably be recommended.

  • FileVault decryption paused, unable to revert

    My 2014 MacBook Pro with OS X 10.10.2 became unusable after a crash where the system became unresponsive and I was forced into a hard reboot. As I was using FileVault, the login screen was appearing soon after rebooting, but would freeze at around 40% after putting in my password, after which the spinning wheel would start. The problem even occurred in Safe Mode.
    In looking for a solution, it was recommended that I decrypt the drive using the Disk Utility. However, I received an error when attempting to decrypt. I switched to the Terminal to try manually performing the decrypt operation using diskutil. Unfortunately, when trying 'diskutil cs revert UUID', I received the error "Unable to modify a FileVault context". I then tried both encryptVolume and decryptVolume, but they gave me conflicting messages at the disk was decrypted and encrypted already respectively.
    Here is a summary of what I see when I run 'diskutil cs list':
    Logical Volume Family UUID
    Encryption Status: Unlocked
    Encryption Type: AES-XTS
    Conversion Status: Converting
    Conversion Direction: Backward
    |
    +-> Logical Volume UUID
    Conversion Progress: Paused
    Revertible: Yes (unlock and decryption required)

    You'll have to erase the volume and then restore the data from a backup.
    If you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
    In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.Select the Erase tab, and then select
              Mac OS Extended (Journaled)
    from the Format menu.
    You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
    Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

  • PSE 7 Problems Fixed in PSE 8

    Since PSE 6 was released, I’ve tracked all the reproducible bugs I’ve encountered and reported to Adobe.  I’ve tested these problems in PSE 8 and listed the results below – problems that appear to have been fixed in PSE 8 are marked [F], and problems that remain unfixed are marked [U].
    Overview
    There’s good and bad news. Adobe has fixed a number of serious bugs in the Organizer, but it has left most unfixed, even though they’ve been present since at least version 6.  Even worse, the two major features introduced in the PSE 8 Organizer, face tagging and the keyword-tags text box, have show-stopper problems. And even worse yet, Full Screen view is now painfully slow with large catalogs.
    The most important fixes address serious problems with PSE’s handling of drives that were introduced in version 6. PSE now notices when a drive’s letter has changed, a problem that has bedeviled many users upgrading or rearranging their drives. Also, PSE now ignores the case of UNC pathnames (network drives), no longer creating duplicate volumes for the same network drive.  Unfortunately, one serious bug remains: PSE still gets horribly confused when there are two drives with the same volume serial number, and it still doesn’t even issue a warning.
    But many long-standing problem areas remain: The Map View is an unusable toy.  The handling of metadata is riddled with bugs.  Folder Location view shows the wrong contents of folders. Searching has numerous bugs making it clumsy and confusing.
    Overall, of all the bugs I’ve reported, PSE 8 fixes 8 of 46 major ones and 8 of 28 minor ones:
    Major
    Minor
    Fixed
    Unfixed
    Fixed
    Unfixed
    File Management and Tagging
    4
    6
    2
    Integration with Photoshop.com
    2
    5
    Map View
    6
    Color Management
    1
    Metadata
    10
    2
    3
    Searching
    8
    5
    User Interface
    1
    1
    5
    9
    Slide Shows
    1
    1
    Editor
    1
    1
    Total
    8
    38
    8
    20
    I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer.  Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer.   Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    New Problems in PSE 8
    [U] PSE 8 crashes or gets intolerably slow after using the new Keyword Tags text box a small number of times.
    On my 4 GB Vista 32 system, PSE crashes after tagging 41 photos.
    [U] If you use the new Keyword Tags text box to apply an existing tag name with a comma in it, PSE will silently create two new tags instead.
    Apply the existing tag “San Francisco, CA” will create two new tags, “San Francisco” and “CA”.
    [U] After applying a tag, the Keyword Tags text box loses keyboard focus and you need to mouse-click in the box again to enter another tag.
    Forcing the use of the mouse defeats the purpose of the Keyword Tags text box, which is to make tagging much faster.
    [U] The Find > Find People For Tagging command locks up the Organizer for about 30 seconds after you click Done (even if you haven’t made any changes), when using larger catalogs.
    On a catalog with 10,000 thumbnails showing, the cursor spins for 30 seconds after clicking done.  But you can work around this by doing a tag search or setting a date range to have only a small number of thumbnails showing before you invoke the command.
    [U] In the Find > Find People For Tagging command, when you select Add Missing Person, you usually can’t resize the selection box by grabbing the lower-right or lower-center handles, which are the handles that most right-handed people are likely to use.
    If you move the mouse very quickly so that it is over the photo before the selection box appears, you can usually resize the box with those handles.  But you have to be very quick.
    [U] The Find > Find People For Tagging command doesn’t do auto-complete on pre-existing People tags, making it very hard to use with existing catalogs.
    I have over two hundred People tags in my catalog.  Because the command doesn’t auto-complete on pre-exisiting People tags and will silently create new tags, and because I don’t remember exact spellings (that’s the point of auto-complete!), I found myself creating duplicate tags (e.g. “John Ellis” instead of “John R. Ellis”, “Bob Smith” instead of “Robert Smith”).  It’s painful to clean up such a mess.
    [U] Full Screen view (F11) is much slower than in PSE 7 on larger catalogs.
    With a 14,000-file catalog and all thumbnails visible, PSE 7 takes 6 seconds to invoke F11, while PSE 8 takes 13 seconds.   With just 20 thumbnails visible (e.g. when working on the most recent import batch), PSE 7 takes 1 second, while PSE 8 takes 7 seconds. This makes selecting the good and weeding out the bad significantly slower.
    [U] PSE doesn’t remember the settings if you toggle the Full-Screen Quick Edit Panel and Quick Organize Panel to disappear completely.
    On 4:3 displays, it’s desirable to hide the panels completely in full-screen view, so you see the entire image without the panels overlapping them (that’s the point of full-screen view, no?).  But PSE forgets the toggle settings, even in the same session.
    [U] The keyword tagging in the Quick Organize Panel doesn’t auto-complete tags you type, making it useless with more than a dozen or so tags.
    It’s worse than useless, since it will silently create a new tag if you mistype the name of an existing one.  And the “tag cloud” is a silly toy that doesn’t help with hundreds of tags.
    File Management and Tagging
    Major Problems
    [F] After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate.  The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
    [F] The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    [F] If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files.  This bug and the previous one with Reconnect had the same underlying cause – the Organizer didn’t update drive letters in its catalog.  Fixed in PSE 8.
    [F] The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
    [U] Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
    [U] The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    I remain mystified that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number.  While most people will never encounter this, when it strikes someone, its symptoms are very mysterious (and a lot of people using cloning utilities).
    [U] The conversion of a catalog from PSE 6 to PSE 8 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup).  As a result, it isn’t possible to save photos in version sets, and PSE 8 will create duplicate thumbnails in the Organizer for an edited file.
    [U] File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
    [U] Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
    [U] When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 8 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
    Minor Problems
    [U] In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
    You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
    [U] Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
    Integration with Photoshop.com
    Major problems
    [F] Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
    [F] If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
    [U] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
    The date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
    [U] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
    [U] Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
    [U] Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
    [U] When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
    Map View
    Major Problems
    [U] It takes 4 seconds to assign a keyword tag to a photo if there are 2,000 or more photos with map locations.
    It takes 2 seconds with 1,000 photos, 6 seconds with 4000 photos, and 11 seconds with 8,000 photos, and 21 seconds with 12,000 photos.
    [U] Map view is unusably slow with more than 8 - 10,000 mapped photos.
    When I imported 12,000 photos (the size of my catalog) that had GPS locations, the Organizer crashed a number of times when I tried to zoom and pan the Map view.   When I selected Limit Search to Map Area, PSE took over a minute to respond.
    [U] Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
    Giving a map location to a tag assigned to 1700 photos makes assigning any keyword tag to a photo very slow, 12 seconds.    Searching on keyword tags and Show All each take 13 seconds.
    [U] Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
    The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
    [U] Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
    [U] If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
    Scrolling the map or restarting the Organizer causes the pin to appear.
    Color Management
    Major Problems
    [U] The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
    Metadata
    Major Problems
    [U] The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
    The PSE 8 Write Keyword Tag command now gives a warning when you try to invoke it on a D300 .NEF raw file. Why PSE can write sidecars for Canon but not Nikon raw files is a mystery – it’s no harder to handle one than the other.
    [U] File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
    [U] File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
    [U] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
    [U] New dates set by Edit > Adjust Date and Time sometimes get silently lost.
    See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
    [U] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
    [U] In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
    [U] If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
    [U] Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
    [U] When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007, e.g. October 31, 2006 12:00 PM.
    Minor Problems
    [F] The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
    [F] When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
    Now, the edited version picks up date/time, caption, notes, and keyword tags, but not the star rating, which could be charitably interpreted as a plausible design decision.
    [U] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
    [U] Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
    [U] With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
    Searching
    Major Problems
    [U] The timeline doesn’t correctly display date ranges spanning many years.
    [U] Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
    The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6, 7, or 8.  Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”.   But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want.  You can also use the text query “not tag:<category tag>”, .e.g. “not tag:places”, but this will exclude all tags containing “places” as part of their name – there is no way to get an exact match of a tag name.
    [U] Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time.
    When the results first display, they are now sorted by Imported From then (correctly) by Date/Time. However, if you click on the Date/Time column header to sort by that column, the dates are sorted alphabetically (incorrectly).
    [U] Find > By History > Imported On takes a couple of minutes on a large catalog, making the command almost useless.
    [U] Find > By History > Imported On shows a scary message “Deleting Keyword Tags” that is apparently harmless.
    [U] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
    Find > By Details > Rating Is Lower Than 1 Star does work.
    [U] Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
    [U] Searching with date ranges doesn’t properly handle time “unknown”.
    Minor Problems
    [U] The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
    [U] Setting a date range and then excluding two tags from the search clears the date range.
    [U] Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
    [U] Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
    [U] When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
    User Interface
    Major Problems
    [?] On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
    I can’t reproduce this in PSE 8.  The Editor’s Print dialog is all rearranged.  But this bug struck some people and not others, so it may be still lurking.
    [U] The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
    Adobe should be embarrassed about this, given that more and more computers are shipping preconfigured with higher DPIs.  See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#The_Organizers_Menu_Bar_ doesnt_show for a workaround.
    Minor Problems
    [F] Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
    [F] In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
    [F] The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
    Well, almost – you can grab the left, right, and bottom edges but not the top.
    [F] Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
    Both the Editor and Organizer don’t show the underline until you let up on the Alt key, whereas other Windows program show the underline when you first press the Alt key.
    [F] The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
    [U] In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
    [U] In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory.  (The command reports the correct amount in the Editor.)
    [U] The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
    [U] Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
    Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
    [U] Dialogs in the Editor sometimes bounce back when you try to move them.
    [U] Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
    [U] In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
    [U] Escape doesn’t close the full-screen-mode Properties dialog.
    [U] You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
    The Editor can now be tiled by Windows Explorer and other window managers, but the Organizer still can’t.
    Slide Shows
    Major Problems
    [F] The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
    PSE now sets the duration to the length of the clip.  You can’t edit the duration, though – you can invoke Edit Duration, but PSE ignores the new value.
    [U] An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
    For an individual slide, you can give the Use Existing Audio Caption command to import that photo’s existing audio caption.
    Editor
    Minor Problems
    [F] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
    [U] The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
    For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.

    John,
    Firstly, my apologies for the length of this post – it has been fermenting a while.  For those in a hurry I have split it into two sections – the first contains some general comments on the situation with PSE (v 7 in my case) and Adobe (as I see it) and the second contains a list of issues that I have encountered and some suggestions for improvement.  As with you, my comments are largely directed at the Organiser module within PSE.
    Part 1:
    Before going any further I’d like to say what an excellent job you’ve done in cataloguing, understanding and in many cases providing solutions to a number of bugs.  Adobe should be paying you a hefty sum for doing this work.  It’s a welcome change from a large percentage of what you read in blogs and forums to see things dealt with systematically, objectively and in an informed way.
    I’m less impressed with Adobe’s approach.  In my opinion, if you choose not to provide program updates to your customers (i.e. you get what you bought in the box and that’s it) then you have a moral obligation to make sure that what you sell is as robust and free of bugs as possible.
    I would be very surprised if they were not well aware of the comments you have made (if they aren’t then that would indicate an appalling failure of their ability to process feedback).  The fact that they have not, in subsequent releases, dealt with all of the issues that have been highlighted is not good.  I would go further and suggest that it is actually a breach of fair trading practice and disingenuous to sell the product as “fit for purpose” knowing these bugs are still in place.
    It’s unreasonable to expect software to be absolutely faultless, and this is why the issuing of updates is a much “fairer” system.  The problem, I think, with Adobe’s approach is that to entice new customers to each release they need to provide new features.  A natural consequence of this is that there is a temptation to prioritise development of new features rather than providing solutions to existing issues.  There is no incentive for Adobe to change this state of affairs for as long as customers are purchasing their products.  In this respect one of the problems is that many of the reviewers to whom prospective customers go will rely on first impressions and will not uncover many of the issues.  Adobe may be comfortable with this situation (and on relying on the reflected aura of Photoshop) but their product is not cheap and there is plenty of scope for competitors to provide a more robust, dependable product at cheaper price.  With free applications like Picasa they will need to be very careful they don’t drop the ball.
    Don’t get me wrong I think the concept of PSE organiser is excellent (I actually prefer it to my experience of Lightroom), it is the quality of execution that I have issues with.
    My first experience of PSE was version 3 and this was positive enough for me to purchase PSE 7.  However, my biggest disappointment with PSE 7, because to me it is fundamental, has been the quality of rendering images in full screen mode.  Yours is the first comment I have seen that comments on the appearance of “jaggies” when displaying images in PSE.  My understanding is that this relates to the anti-aliasing which is carried out when converting from image to display resolution and the level to which this smoothes out gradients in hue, saturation and luminance.  I never observed this problem is PSE 3.  Although the degree of anti-aliasing is a subjective preference, I was deeply disappointed and still find it hard to believe that free or bundled software (picture manager, windows picture viewer, etc) can manage this when PSE 7 can’t.
    Anyway, I’m not sure how to illicit a change from Adobe.  One way is to write the sort of rant I have above although I doubt this will make much difference.  In any case keep up the good work and hopefully something will come of it.
    Part 2:
    Some issues I’ve encountered:
    Migration from Windows XP to Windows 7 – change in directory structure means that the “documents and settings” part of the user directory path in XP (i.e. c:\documents and settings\<<username>>\etc.) is now a shortcut which redirects you to the new location for user files which is c:\users\<<username>> \etc.  If you are migrating from an old XP machine to a new Windows 7 one, you’ve kept your username the same and you have tried to retain the same directory structure then PSE 7 will still find files in your catalogue with the old style path.  However, it will not recognise duplicates if you accidentally re-import the same files now they are on your Windows 7 machine.  My workaround for this is to use an external file manager (e.g. windows explorer) to change the name of the directory that contains all of your photos.  This causes PSE 7 to fail to resolve the path locations.  You can then can select the relevant files and reconnect using the reconnect facility (File-Reconnect-Missing Files);
    Watched folders are lost for any drive other than C when PSE 7 is closed and then reopened;
    Duplicate files are not recognised and can be imported if they are not on the C drive (i.e. on an external drive);
    Selecting a category selects all of the keyword tags/subcategories beneath it but excluding it does not exclude all of the keyword tags/subcategories beneath it; however, both selecting and excluding a sub-category selects and excludes the tags/sub categories beneath it;
    Searches bring back the entire version set or stack even if only one of the files within meets the search criteria;
    The instant search facility will sometimes decide that a number typed in is a date and will not find some files you would expect it to e.g. those where the number typed in is part of the filename rather than a date;
    Anti-aliasing is insufficient – jaggies appear on jpegs displayed at certain zoom level.  Interestingly this does not seem to occur if a jpeg has been created from a raw file through PSE 7 rather than an external application (at least for the camera I have).
    Some suggestions:
    Find duplicates facility;
    Sort by filename and other file data;
    Hide directories in the folder directory pane of the folder view if they contain no imported files – in PSE3 this was the only option and was actually quite useful to confirm that there were no imported files in a certain location (e.g. if e:\...etc was not in the list then you knew that you had no imported files located on the e:\ drive).  It would be good to have this a display option.
    Allow filters to be applied only to selected files;
    Allow files to be rotated in the organiser without actually resaving them as a rotated file.

  • Problem fixing hard drive errors

    I own Toshiba Satellite A250. My hard drive is probably before major failure. I am trying to fix the errors as running the command chkdsk c:/f  from command prompt but this can't fix the errors.
    How should i proceed?
    I don't know what exactly is wrong with the hard drive but sometimes when starting laptop it freezes right after loading the bios. I thought it is a problem with the bios but it seems that it is a problem with the hard drive.

    How did you test the RAM? Use www.memtest.org
    It could be a mainboard or VGA Board failure.

  • This problem showed up last year spent 2 months with apple senior supervisor for tech support no solution. When the "new" itunes came out problem fixed its self. Just did an update last week or so and back to the problem. In "get info" missing all rt side

    Last year upon an update some of my itunes media was not working. Then the new version came out and it fixed itself.
    Well another update and we start over with the problem. In the itunes store you can not preview any tv show, music video, or movie.
    In your itunes library none of the purchased movies, tv shows, or music videos play. The element the same is in the get info tab. The information in the right side pane in the middle is gone. The left side information is still present. The right side info is the purchase info. Even an item downloaded today had the missing info and will not play. After dealing with apple support with the first go around last year. I uninstalled and reinstalled itunes 8 or more times, in the proper order. I deleted my itunes library and reinstalled it. We deleted all types of program files and program data. nothing worked. I was trying things on my own and foung nothing. Please help I am so frustrated with this. It seems to be a codec error that I can not solve.

    Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you.
    Please go to your profile page for the forum, and look in the middle, right at the top where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.
    Under “My Support Cases” you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis as the agent may be waiting for information from you before they can proceed with any actions.
    To ensure you know when they have responded to you, at the top of your support case there is a drop down menu for support case options. Open that and choose "subscribe".
    Please keep all correspondence regarding your issue in the private support portal.

  • Is the Random Media Encoder CC Mute Problems Fixed?

    There is a thread about Mute/Solo but here: http://forums.adobe.com/message/5592142#5592142
    However it has been quite some time since Adobe staff has responded to that thread, so I thought I'd create a new thread to see if it is fixed. Right now I'm wasting alot of time with Premiere Pro CC / Adobe Media Encoder CC as this combination will produce encodes with randomly muted audio tracks, effectively making Adobe Media Encoder unusable. Because I and other CC users rely on Media encoder for their batch export workflow, I'm wondering if Adobe has addressed the problem in the newest release Premiere Pro CS 7.0.1 (105) or not. Please respond so I can use Adobe Media encoder again!
    Thank you.

    This is causing massive headaches for me, and has wasted me days of work. I have a 12 language, 21 sequence DVD project, with all the languages on one timeline. Initially I used mute and solo to export the various language versions. But, due to whatever bug is going on, only around a third of the audio clips exported properly. Many muted or kept the wrong audio tracks, others muted them all.
    So then I had to create 152 sequences from my original sequences, one for each language for the 21 different clips, then going through and deleting all but one lanuage for each (not ideal if there are any changes in timings to the original sequences). I then exported these as dolby digital audio for DVD. No success - only one of the languages exported. The rest just had the music track. So then, I tried exporting AAC audio. Two of them worked, the rest didn't. It seems totally random when exporting from media encoder which tracks actually appear in the final file. Some are muted, some aren't. And it is even different depending on what file format is being exported.
    It seems I'm going to have to export, one-by-one, the audio clips from Premiere. 152 times. I don't want to have to, but if Media Encoder can't do the job it's suppoed to do, then as far as I can tell, that's the only alternative. Not happy at all. My CTRL-E fingers are going to get tired.
    Can any Adobe staff tell us whether these bugs are going to be fixed at any point?

  • PSE 6 Problems Fixed in PSE 7

    Over the past year, Ive kept a list of PSE 6 problems Ive encountered and verified:
    http://www.adobeforums.com/webx/.59b65e1b/0
    Ive tested those problems in PSE 7 on my computer, and the results appear below.
    PSE 6 problems that appear to have been fixed in PSE 7 are marked [F], and problems that arent fixed are marked [NF]. Because of limitations of the forum, this list is split across several messages.
    Overview
    The good news is that Adobe has fixed many of the most serious problems with PSE 6:
    - The missing Help content.
    - The inability to use raw files on a newer computer.
    - The Move command that deleted files.
    - The low-contrast grey-on-black user interface.
    In addition, the PSE 7 Organizer seems significantly zippier for scrolling and searching (with my 13K catalog and someone elses 68K catalog).
    The not-so-good news is that a fair number of serious problems and a large number of minor ones remain unfixed:
    - The Organizer still gets horribly confused by reassignment of drive letters and drives with duplicate serial numbers, situations that occur when people upgrade their computers.
    - Numerous problems with searching, including the broken timeline and exclude keyword category.
    - Folder Location view still shows incorrect folder contents.
    - Map view remains a buggy toy that cant handle more than several hundred photos.
    - Date/times set by Adjust Date and Time can still be lost silently.
    - High-resolution displays with DPIs larger than 96 arent supported.
    - The Organizer shows incorrect colors for Adobe RGB photos.
    There are 65 issues listed here, 37 of which are major, causing data loss or seriously impeding functionality with no easy, obvious workaround. Of the 37 major issues, 13 have been fixed. Of the 28 minor issues, 8 have been fixed.
    Ive reported all of these problems to Adobe. Almost all of them are in the Organizer. Based on all the reports on the forums, it appears that the PSE 6 Editor has far fewer problems the Organizer. Perhaps thats because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange laptop with a dual-core 1.8 GHz processor, 3 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    Raw Files
    Major Problems
    [F] On a multiprocessor, the Organizer behaves erratically with catalogs containing raw files: sometimes it crashes, sometimes it shows the hourglass icon for raw files, sometimes it shows the broken-image icon.
    [F] In a catalog with large numbers of raw files, scrolling quickly over dozens or hundreds of large-sized thumbnails will consume 100% CPU for a minute or longer.

    Part II
    File Management and Tagging
    Major Problems
    [F] The File > Move command will silently and permanently lose a file if the destination folder has a file of the same name as the file being moved; this is different behavior than PSE 5.
    [F] The File > Move command loses the association between the photo and the audio caption, even though it moves both files to the new location.
    [F] If you move or rename a catalog using File > Catalog > Move/Rename, you can no longer edit existing slideshows in the catalog.
    [F] Tag hierarchies with more than 500 or so tags make the Keywords pane unusably slow (but worked fine in PSE 5).
    [F] The Photo Downloader process APDProxy.exe crashes at startup because of a missing DLL.
    ]This problem doesnt occur in my PSE 7. But it was clearly a timing-dependent bug (a race condition) that came and went for me and many others, so it may be still lurking. Adobe has a tech note that says it occurs with PSE 7, but the tech note gives symptoms and a workaround that only apply to PSE 6, suggesting a cut-and-paste error by a PSE 7 support person.
    [NF] The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    ]Im very disappointed that Adobe didnt add the three lines of code that would have issued a warning when it discovered two drives with the same number. While most people will never encounter this, when it strikes someone, its symptoms are very mysterious. Adobes tech note on the issue gives incorrect and misleading information about possible solutions.
    [NF] The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    [NF] If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    ]This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files. This bug and the previous one with Reconnect have the same underlying cause the Organizer doesnt update drive letters in its catalog.
    [NF] Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    ]Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they havent been easy to reproduce.
    Minor Problems
    [F] The File > Rename command no longer includes leading zeroes, causing the renamed files to sort incorrectly in Windows Explorer.
    [F] Display > Import Batch shows the wrong time for batches imported by the Photo Downloader; if the local time zone is UTC-8:00, then the time will be 8 hours earlier.
    [F] The Organizer doesnt unlock an edited file saved to a folder whose name contains an apostrophe.
    [NF] In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
    ]You can get files named 1.jpg, 2.jpg, etc. but you cant get files named p1.jpg, p2.jpg, etc. a hyphen is still added in that case.
    [NF] Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
    Map View
    Major Problems
    [NF] Map view is unusably slow with more than about 6-8,000 mapped photos.
    ]When I tested PSE 7 by importing 12,000 photos (the size of my catalog) that had GPS locations, the red push-pins didnt blink uncontrollably as they did in PSE 6. But the Organizer crashed a number of times when I tried to zoom and pan the Map view until I was able to scroll the map to another country and then back again. The CPU continued to consume 80% of a single CPU (40% of two), even 10 minutes after I closed Map view. When I selected Limit Search to Map Area, PSE took over a minute to respond.
    [NF] It takes 5 seconds to assign a keyword tag to a photo if there are 1,000 or more photos with map locations.
    ]In PSE 7, it takes 3 seconds with 1,000 photos, 12 seconds with 8,000 photos, and 18 seconds with 12,000 photos.
    [NF] Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
    ]Giving a map location to a tag assigned to 2000 photos makes assigning any keyword tag to a photo very slow (see above). Searching on keyword tags takes 15 seconds, and a Show All takes 15 seconds.
    [NF] Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
    ]The weird thing is that assigning a map location to the tag doesnt try to write the metadata of files with that tag.
    [NF] Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
    [NF] If a photo with GPS coordinates is imported, it doesnt show as a red push-pin on the map.
    ]Scrolling the map or restarting the Organizer causes the pin to appear.

  • Photoshop CS4 (64bit) & Win7 x64 problem fixed

    I just wanted to post this to help anyone who might be having this problem.
    Here's the problem. When you use Photoshop's lasso tool, you can press ALT at the same time, and it would turn into a magnetic lasso tool that you can use to make straight lines.
    Well, what would happen is that I would be making a selection, and then suddenly the screen (both screens, as I'm using a dual screen setup) would flicker, and the selection would complete by itself, and I would be SOL, as, obviously, the selection is not what I wanted.
    I could replicate this without fail. I'm halfway done with making a perfect selection, and bam!, this crap happens, and I have to start all over again. It happens ALL the time, no matter what Photoshop setting I used. Photoshop was completely updated, and all my device drivers (video card, mouse drivers, etc.) were all at their latest. So I started looking outside Photoshop, as I was thinking it might be another software problem.
    After much trial and error, I narrowed it down to Task Manager. I had Task Manager running in my tray. If I closed Task Manager (not minimize, close), restarted Photoshop, and made my selection using the lasso tool, the issue would go away, but would come back randomly.
    The fix? Run Photoshop CS4 in Vista compatibility mode. This solves the problem completely.
    I know a lot of you will probably say that you have Photoshop CS4 running flawlessly on Win7 x64, but I have 3 computers, each with completely different configurations, one of them being a laptop, that I was able to replicate this on. Once I ran Photoshop in Vista compatibility mode on each computer, the problem was completely solved.
    So I hope this helps anyone who has run into this problem.

    I confirm he is a blond wanna be.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Hudechrome wrote:
    It won't work for me. I never used Vista.
    (I will neither confirm or deny I am a blonde!)
    Thanks for sharing.

  • XML Problem: I can't open my Word 2007 docx file (Start/Endtag Problem) - Fixit doesn`t work

    Hi there,
    I have a big problem and I hope there is somebody who could repair my Word-Document (or at least save the text somehow).
    After my flash drive crashed, I used a data restoring software and managed to get back this important Word-File, but now I can't open it ((Start/Endtag Error)
    The Fixit solution of Microsoft didn't work. I read about fixing the problem with an XML-Editor, but I have no experience with that.
    The most important thing would be just the text. It would be fantastic if someone could restore this work (which took me nearly two weeks).
    I uploaded the docx and the xml file here:
    http://www.file-upload.net/download-8602999/Studienarbeit_-_Anw._Fallstudienseminar_-_Robert_Fromm_-_32874.docx.html
    http://www.file-upload.net/download-8603008/document.xml.html
    Thanks a lot in advance! You would save me a lot of time.
    greetings Robert

    Hi,
    I had download the file ,but your second link was invalid. I tested to open it, and got the error message:"The name in the end tag of the element must match the element type in the start tag."
    This issue is related strictly to oMath tags and occurs when a graphical object or text box is anchored to the same paragraph that contains the equation.
    Please try to fix it with the KB:
    http://support.microsoft.com/kb/2528942/en-us
    Here is a similar issue:
    http://answers.microsoft.com/en-us/office/forum/office_2010-word/cant-open-word-file-because-of-end-tagstart-tag/581159d0-9ebc-4522-b30c-53e33e8268e1
    Regards,
    George Zhao
    TechNet Community Support

Maybe you are looking for