Update Kills Format Compatibility

This morning, Adobe Updater updated Premiere, After Effects, and Media Encoder.  Now when I open any of my Premiere projects, including one I was working on this morning, all MPEG files show up as offline.  When I try to Link Media, Replace Footage, or even reimport it, I get the error message "Unsupported format or damaged file."
This is bad, as a LOT of my footage is in mpeg format.

Well, for what it's worth, I've had this (or at least a similar) problem twice now, both immediately following the major updates to Premiere Pro.
I updated, restarted, launched my project and was met with some message about "trial version" and "unsupported" and "media," although I forget the exact statement. The gist of it was that something was wrong, and it seemed as though the prompt was telling me to purchase a full version. I mainly have DV footage, but every now and then, an MPEG variant file shows up in a project.
Working on Vista Ultimate x64
At any rate, I didn't do anything special....I think I might have closed the application, and maybe restarted, or perhaps even done another update check. Whatever I did, something that broke during the update process re-connected once I did....erm, whatever I did.
So I know, not an incredibly helpful post here, but I wanted to further assert that 1) this problem seems almost entirely connected to the updating process, 2) it appears to be fixable without any reinstalling or cleaning or anything (because I did nothing of the sort), and 3) well, I don't have anything for 3, but only making 2 points seems a little short on an already (possibly) useless, uninformative post.
Hope this helps somebody (maybe even Adobe..............ahem..........)
PS - wanted to mention, my username on here used to be SCAPsinger (before the forum switchover), so that should help you all know what kind of dude you're dealing with here. Use that extra bit of information however it may suit you.

Similar Messages

  • Isit true to say that iPod Updater kills your iPod?

    Hello all,
    First, sorry for my poor English. I am not a professional nor a technician and I could be wrong, so please correct me. There are many problems reported mainly from the PC users that their iPod can't be recognized nor mounted after the installation of the latest iPod updater. Most of them claimed that the iPod updater kills their beloved iPods. Before we jump to a conclusion, we must understand what is iPod, and how does the iPod update work.
    I believe that iPod equals a basic computer and need a OS in order to communicate with the PC. Installation the Updater will format the Hard disk of the iPod and then install the simple OS, so if we open the iPod updater file, it will show a window with two buttons i.e. Restore and Update, an Update is to copy the latest OS over the old version, but the Restore will format the hard disk before it install the OS over it. And importantly, during this process, the iPod needs sufficient of power to complete the upgrade, however, the problem comes just after the format, and the PC's USB (only 2 will work not 1.1) does not supply the stable power,even some cases that iPod does not get charge in the half way of installatin (a proper installation, you will see a running bar showing on the iPod screen just after the format), so you can imagine a hard disk got format but only got an uncompleted OS, of course, the iPod would not get recognized and mounted, and do not manage to communicate with the computer. At this stage the iPod will show a Sad iPod icon, a folder with exclamaiton points or a battery charging icon.
    So, what would you do when it reach at this stage, a Reset would not work, and you would not able to do the Restore as the iPod is totally unrecognized by the computer.
    Therefore, is there anyway to solve this problem, in my opinion and from my past experience, the answer is "yes", the simple way is to put your iPod in Disk Mode, when it plug to the computer, it will show as an external Hard Disk, you must fix it by doing a format (RESTORE would not work at this stage as it still can't recognized and mounted), in Mac we can use "Disk Utility" but the XP would not allow you to do the format in FAT32. After the formatting, replug the iPod with the computer, then it can be mounted and allow you to do the RESTORE.
    In addition, I find an interesting point is, if your iPod formatted with a Mac, you will have better chance to be mounted with a PC, even your iPod does not complete the process of the installation of the iPod updater, and a PC formatted iPod will be likely to be fixed by a Mac as well.
    How should we do before the update of the lastest software, for the XP user please do the following:-
    1. Go to the system restore and create a check point in order to revert back to the previous version of the iPod updater, or do the back up using the 3rd party software such as Ghost or Go Back.
    2. To have a test and make sure the PC's USB works properly. You can use the iPod or a PDA, and just make sure it got charged.
    3. Have your iPod a full charge before the installation of the iPod updater
    So, who is the main killer for the iPod?
    For further infomation please read the following link - which wrote by a groups of great people - thank your guys
    http://discussions.info.apple.com/webx?128@@.68ae8668

    Yes, it will erase all your data with your iPod. Please do not format until you have the back up of your iPod. Very likely that your iPod was formatted by a Mac, which can't be read by your PC. Download a software called Xplay
    http://www.mediafour.com/products/xplay/

  • Latest Acrobat X Update Killed Com1

    The latest Acrobat X update killed my Com1 port. Yes, I still use Com1 to communicate with my ham radio. So if any Adobe guy is reading the discussions in this form, please fix this bug. BTW, why do I have to call tech support, why can't I send you guys an e-mail.
    . . . JohnB

    To correct the port problem of Adobe PDF Printer after the application of A10.0.1 patch kindly follow the below steps (they require Admin privileges):
    1.      Go to Devices and Printers.
    2.      Right Click on the Adobe PDF printer and click on Remove Device (Win 7). This will delete the Adobe PDF printer.
    3.      Go to Programs and Features (Win 7)
    4.      Select Adobe Acrobat X Pro or Standard and click on Change
    5.      Select Repair and follow instructions to complete repair
    6.      After the repair is done you will have correct settings of Adobe PDF printer and also Adobe Acrobat version 10.0.1.

  • MacOS X 10.4.9 Update Killed My Mac!

    Today I tried to install the 10.4.9 update.
    Something went wrong when installing the update and I got an error message saying that the installation was unsuccessful.
    After restart my mac got stuck on the grey screen with the Apple logo and a wheel spinning forever.
    Fortunately I fixed the issue: http://net3x.blogspot.com/2007/03/macos-x-1049-update-killed-my-mac.html

    Most likely, you could have avoided this problem if
    you had followed Apple’s instructions for properly
    installing software updates:
    Troubleshooting installation and software
    updates
    Note that Apple doesn’t mention anywhere the need to
    repair permissions either before or after installing
    a system update, not even for troubleshooting system
    update issues. It’s the disk itself (i.e. the
    filesystem) that should be verified/repaired
    before installing anything. Note also that no
    applications should be running while installing the
    update and that you may experience unexpected results
    if you have third-party system software modifications
    (not normal applications) installed.
    I have to call complete and utter BS on this. I have been a mac user for more than 3 years. I have updated the day of almost every major update since 10.3.1 and 10.4.9 is by far the most problem prone thing I have ever seen apple put out. I have never once had a single issue where my mac would not boot after the install of an update. Now I have updated both my MacBook and Intel Mac Mini and both were dead in the water after the install. A different software suite is on both systems, and there is no "intrusive" 3rd party software that should cause any trouble. Thanks to the instructions above I was able to get back on-line and running 10.4.9, but something really needs to be done about these issues.

  • "Lightrrom couldn't update the format of its catalog file and must quit. ..".

    I had no trouble updating my small catalogs but my large one I tried several times. After around 45 minutes I see a dialog box that says
    "Lightroom couldn't update the format of its catalog file and must quit. Your previous catalog will be restored".
    Any help on how I can get LR to open the catalog. No problems with the integrity check. The catalog was working just fine in version 1.0.

    I had the same issue.
    Fortunately I had backed up up my db before the upgrade.
    I exited then restarted LR and created a new db - so it would start.
    With my backup copied to a safe location I then opened the backup db. The conversion completed successfully and everything appears OK.
    Hope this may help
    Rob

  • Kernel updates kill my luks encrypted system

    All right, this is weird. I have a 64bit system with encrypted root, home and  swap partitions. To setup I followed the wiki here:
    https://wiki.archlinux.org/index.php/LUKS
    My swap is encrypted like described here:
    https://wiki.archlinux.org/index.php/LU … sk_support
    Since the updates to kernel 3.1 each new kernel update kills my system. Pacman says while upgrading
    [2011-11-08 08:21] >>> Updating module dependencies. Please wait ...
    [2011-11-08 08:21] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-11-08 08:21] ==> Building image from preset: 'default'
    [2011-11-08 08:21] -> -k /boot/vmlinuz-linux_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img_64
    [2011-11-08 08:21] ==> Starting build: 3.1.0-3-ARCH
    [2011-11-08 08:21] -> Parsing hook: [base]
    [2011-11-08 08:21] -> Parsing hook: [udev]
    [2011-11-08 08:21] -> Parsing hook: [autodetect]
    [2011-11-08 08:21] -> Parsing hook: [pata]
    [2011-11-08 08:21] -> Parsing hook: [scsi]
    [2011-11-08 08:21] -> Parsing hook: [sata]
    [2011-11-08 08:21] -> Parsing hook: [usbinput]
    [2011-11-08 08:21] -> Parsing hook: [keymap]
    [2011-11-08 08:21] -> Parsing hook: [usb]
    [2011-11-08 08:21] -> Parsing hook: [encrypt]
    [2011-11-08 08:21] -> Parsing hook: [openswap]
    [2011-11-08 08:21] -> Parsing hook: [resume]
    [2011-11-08 08:21] -> Parsing hook: [filesystems]
    [2011-11-08 08:21] ==> Creating gzip initcpio image: /boot/initramfs-linux.img_64
    [2011-11-08 08:21] ==> Image generation successful
    [2011-11-08 08:21] ==> Building image from preset: 'fallback'
    [2011-11-08 08:21] -> -k /boot/vmlinuz-linux_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img_64 -S autodetect
    [2011-11-08 08:21] ==> Starting build: 3.1.0-3-ARCH
    [2011-11-08 08:21] -> Parsing hook: [base]
    [2011-11-08 08:21] -> Parsing hook: [udev]
    [2011-11-08 08:21] -> Parsing hook: [pata]
    [2011-11-08 08:21] -> Parsing hook: [scsi]
    [2011-11-08 08:21] -> Parsing hook: [sata]
    [2011-11-08 08:21] -> Parsing hook: [usbinput]
    [2011-11-08 08:21] -> Parsing hook: [keymap]
    [2011-11-08 08:21] -> Parsing hook: [usb]
    [2011-11-08 08:21] -> Parsing hook: [encrypt]
    [2011-11-08 08:21] -> Parsing hook: [openswap]
    [2011-11-08 08:21] -> Parsing hook: [resume]
    [2011-11-08 08:21] -> Parsing hook: [filesystems]
    [2011-11-08 08:21] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img_64
    [2011-11-08 08:21] ==> Image generation successful
    So the generation of the initramfs seems to be ok.
    But when I reboot this box, I get:
    running hook [openswap]
    device /dev/sda4 doesn't exist or access denied
    running hook [resume]
    waiting 10 seconds for device /dev/mapper/swapDevice
    waiting 10 seconds for device /dev/mapper/root
    root device /dev/mapper/root doesn't exist. Attempting to create it.
    ERROR: unable to determine major/minor number of root device /dev/mapper/root
    /dev/sda4 is my swap partition. Then I get dropped to a recovery shell which I can't use because my (usb) keyboard is not working.
    Now the funny part. I start the box from a install cd and chroot into the existing installation. I do a
    mkinitcpio -p linux
    The initramfs is regenerated and it works again! What the hell is pacman doing other than regenerate the initramfs with my presets?
    Harvey
    Last edited by Harey (2011-11-12 16:10:48)

    New kernel 3.1.1 did it again. My system hangs in initramfs after the reboot. Same as before: a simple rebuild without any changes fixed the boot process. This time I was able to backup the 'bad' initramfs before chrooting in and rebuilding.
    it is very funny to see the content of the 'bad' initramfs image - it is nearly empty!
    ==> Image: /boot/initramfs-linux.img_64.bak
    ==> Kernel: unknown
    ==> Compressed with: gzip
    -> Compression ratio: .452
    -> Estimated decompression time: 0.036s
    ==> Included binaries:
    /sbin/dmsetup
    /sbin/cryptsetup
    /sbin/udevadm
    /sbin/blkid
    /sbin/modprobe
    /bin/busybox
    ==> Hook run order:
    udev
    keymap
    encrypt
    openswap
    resume
    The rebuilt image looks like this:
    ==> Image: /boot/initramfs-linux.img_64
    ==> Kernel: 3.1.1-1-ARCH
    ==> Compressed with: gzip
    -> Compression ratio: .593
    -> Estimated decompression time: 0.047s
    ==> Included modules:
    aes_generic fcrypt hid-roccat-kone rmd160
    aesni-intel ff-memless hid-roccat-koneplus rmd256
    aes-x86_64 gcm hid-roccat-kovaplus rmd320
    af_alg gf128mul hid-roccat-pyra salsa20_generic
    ahci ghash-clmulni-intel hid-samsung salsa20-x86_64
    algif_hash ghash-generic hid-sjoy scsi_mod
    algif_skcipher hid hid-sony sd_mod
    ansi_cprng hid-a4tech hid-speedlink seed
    anubis hid-apple hid-sunplus seqiv
    arc4 hid-axff hid-tmff serpent
    async_memcpy hid-belkin hid-topseed sha1_generic
    async_pq hid-cherry hid-twinhan sha256_generic
    async_raid6_recov hid-chicony hid-uclogic sha512_generic
    async_tx hid-cypress hid-wacom snd
    async_xor hid-dr hid-waltop snd-rawmidi
    ata_piix hid-elecom hid-wiimote snd-seq-device
    authenc hid-emsff hid-zpff soundcore
    authencesn hid-ezkey hid-zydacron sr_mod
    blowfish hid-gaff hifn_795x syscopyarea
    camellia hid-gyration hmac sysfillrect
    cast5 hid-holtekff jbd2 sysimgblt
    cast6 hid-kensington khazad tcrypt
    cbc hid-keytouch lcd tea
    ccm hid-kye libahci tgr192
    cdrom hid-lcpower libata twofish_common
    crc16 hid-logitech lrw twofish_generic
    crc32c hid-magicmouse lzo twofish-x86_64
    crc32c-intel hid-microsoft mbcache uhci-hcd
    cryptd hid-monterey md4 usbcore
    crypto_null hid-multitouch md5 usbhid
    ctr hid-ntrig michael_mic usb-storage
    cts hid-ortek padlock-aes vmac
    deflate hid-petalynx padlock-sha wp512
    des_generic hid-picolcd pata_acpi xcbc
    dm-crypt hid-pl pata_jmicron xor
    dm-mod hid-prodikeys pcbc xts
    ecb hid-quanta pcrypt zlib
    ehci-hcd hid-roccat raid6_pq zlib_deflate
    ext4 hid-roccat-arvo raid6test
    fb_sys_fops hid-roccat-common rmd128
    ==> Included binaries:
    /bin/busybox
    /sbin/udevadm
    /sbin/dmsetup
    /sbin/blkid
    /sbin/cryptsetup
    /sbin/modprobe
    ==> Hook run order:
    udev
    keymap
    encrypt
    openswap
    resume
    For some reason the initramfs built by pacman is missing all modules. To say it again, nothing changed, simple rebuilt by mkinitcpio -p linux!
    This seems to be a bad bug...
    Harvey
    Last edited by Harey (2011-11-12 16:07:09)

  • I have an iPhone 4S with Sprint, I had to replace my last phone after the newest update killed my wifi button. Now my new phone won't get 3G at all. I have tried turning my phone off/on, resetting my networks, and turning airplane mode off and on.

    I have an iPhone 4S with sprint. I had to replace my phone after the new update killed my wifi button and wouldn't let me turn my phone off. Since I've had my new phone, I haven't been getting 3G. I have tried resetting my networks, Turing airplane mode off/on and restarting my phone. Nothing seems to work. Any info on what I should do next would be great.

    If you have set this phone up, then there would not necessarily be a solution here until you have been verify with the provider that everything is provisioned correctly on their end. Since the 3G comes from your cellular provider, if the settings are correct on the phone, then you should work with the carrier next.

  • Flash updates kills sound

    I have a Mac 10.6.8 which on the last Adobe Flash update killed my sound.
    I know nothing of computers - it is a glorified typewriter to me, so please advise how to remedy this in simple terms.
    Technical terms are the death for me!

    Hi,
    Could you please let us know some more details?
    Please go to the following page and let us know the Flash Player version and browser you use: http://helpx.adobe.com/flash-player/kb/find-version-flash-player.html#main_Find_the_Flash_ Player_version_installed_on_your_machine
    Do you mean to say you don't hear any sound at all?
    Thanks,
    Sunil

  • Will FC Express be updating its format soon?

    I was wondering if anyone has heard if FC Express was going to update its format anytime soon. I am looking into buying a new camcorder, and I don't want to be as limited to what I can buy as I am right now. Obviously, right now it only supports DV and HDV, what about avchd, or m-peg, or any of the other formats. If anyone has any info on this, I would appreciate it. thanks

    Speculation about future releases is prohibited by the terms of usage of the forum. Nobody knows anyway.

  • Please help: 10.4.3 update KILLED iCal

    After updating to 10.4.3 all my iCal data was gone. I restored it using Backup and when I launched iCal it all appeared as normal—and then a few seconds later, poof, it all disappeared again right before my eyes. I tried making a new entry and at first it didn't seem to work, then all my iCal data reappeared for a few seconds, only to disappear again a few seconds later, leaving iCal "virgin" as if no entry had ever been made. If I quit and reopen iCal, I can again briefly see the calendars before they disappear.
    The current iCal version is 2.0.3. I have tried erasing preferences and starting over again to no avail, as well as logging in with the shift key down. I have also repaired the disk and the permissions with no improvement.
    Any suggestions anyone? Is it possible to reinstall just iCal? I really really don't want to have to do a complete system reinstall because of this stupid bug.

    I don't believe the 10.4.3 Update killed iCal and if a bug, it must be selective since I didn't experience the same and I haven't seen the same reported here in large numbers.
    What is your hard drive capacity and available free space?

  • 10.8.3 update kills cd-roms created with Mac OS Standard HFS format

    Archived CD's created with HFS (MacOS Standard in get info) would mount and you could copy and open documents with no problems a couple of weeks ago in 10.8.2. But after 10.8.3 update are now mounting but you cannot copy or open the files on them.
    Below a CD in finder under 10.8.3, while trying to copy to desktop and trying to open from CD.
    Below same CD in finder of 10.8.2. CD contents show with thumnail preview and the document opens from the CD no problem.
    Why would Apple drop support for HFS in an incremental update with no documentation able to be found anywhere? Any ideas?

    I can't reproduce that. I have a very old backup CD, made in April of 2000 and using the Mac OS Standard format. It works just fine on my 10.8.3 system:
    As you can see, I can open an image file on that CD just fine.
    It's important to note that home-burned CDs don't last forever. They have a limited shelf life, and if they're being used (and exposed to light) frequently, that life will be shorter. All CDs will eventually fail, and I'm guessing that's what happened with yours. Perhaps they are failing in a way that 10.8.2 could deal with, but 10.8.3 can't? I don't know.
    I did see some very strange behavior from the first disk I tried, which was also Mac OS Standard, but was much older (it had no date on it, but I'm guessing mid-90s). Files would show up very briefly, then would disappear from view. Even the Terminal behaved oddly when trying to list the contents. Trying to copy folders to the hard drive resulted in -43 (ie, file not found) errors. It looks like that disk has failed.

  • Update PC formatted i Pod on mac? and podcast synching questions

    I have my 30G iPod formatted for PC, b/c I use it as an external drive. iTunes 7.0.1 on my mac (my home base for synching music, games, podcasts, etc) says it can't update a PC formatted iPod.
    I can't synch the game I bought, but that wouldn't be enough to make me try to update to 1.2 if I wasn't having problems with my podcasts synching. Most synch properly, some don't. I get the message that says my software is too old. I can't seem to manually drag the problem 'casts either. They are just regular podcasts, with no chapters or video.
    Any advice would be appreciated.
    For example, can I download iTunes 7 to a windows machine and update my PC iPod over there? will it wipe all my music? I considered this, but it would be a pain to re-load everything. Would this help the problem?
    Thanks, jenn
    G5 Mac OS X (10.3.9)
    G5   Mac OS X (10.3.9)  

    just read a bunch of posts about how updating to 1.2 on a PC might kill my iPod, so I guess I won't even try to update anything for a while.
    thanks for the warnings, and oh well on the missed podcasts I guess.
    PS- I did try putting the "bad" podcasts into a playlist but that playlist won't copy back to the iPod.

  • Acrobat X Update "killed" Acrobat 9

    Our prepress department uses Acrobat 9 Pro with the Pitstop plug-in to process files. A co-worker working in Windows noticed that he had an update available -- for Acrobat X -- so he went ahead and let it update. (I'll note here that we are in the habit of having multiple versions available, so he assumed he could still use the Acrobat 9 workhorse as needed.)
    He's not happy with X's user interface (and his Pitstop plug-in lives in version 9), so he tried opening files back in version 9. Now suddenly he finds that he cannot run Acrobat 9 at all. Even if he selects it directly. PDFs now open exclusively in version X.
    Is there an "uninstaller" for Acrobat X, and if he runs it, will it break anything else? Will he have to reinstall Acrobat 9 and Pitstop?

    I zip back and forth between versions, so it can be done with a bit of patience and luck. What you have to give up the idea of is that double-click-to-open is any use to you any more. You need to use File > Open or similar.
    Try
    1. Reboot
    2. Use task manager to make sure no Acrobat.exe is running
    3. Try starting Acrobat 9.
    4. Still starts X? Kill it, repeat step 2, and navigate to the acrobat.exe file for v9 and run that.
    5. Still starts X? Right click, properties, check version. Maybe someone/something actually overwrote the app.
    But always remember once you have it working that it is "unsupported" and what that really means. (It is NOT a statement that it never works.)

  • Shockwave player updates: graphics card compatibility problems?

    I've recently had a new problem reported to me in the Driveway Visualiser, a piece of Shockwave 3D content that I've been maintaining since we built it in 2008.  I'm wondering if  recent updates to the Shockwave Plugin (e.g. 11.5.8.612) may be contributing to this...
          www.marshalls.co.uk/transform/driveway_visualiser/dv.asp
    So I'd be interested to know if anyone else has had any new problems affecting old content. I tried reverting the dcr file to last year's version but the same problem still occurs, so it doesn't seem to be a recently-added bug in my code.  I think it could be either a compatibility problem between the graphics card and the plugin, or between the Director 11.0 dcr and the Shockwave 11.5 web player.
    Because we need the DirectImage Xtra, it's Windows only.  For  each different computer that we've tested, the Driveway Visualiser (DV) will either always  work or always fail on that machine - regardless of whether IE or  Firefox is used.  All the test machines have DirectX 9.0c; all are  running Win XP SP3 apart from one laptop with SP2 and Intel 965 chipset  on which the DV fails.  Only one has Director (11.0) installed, and on  that the DV always works.  The problem is much more common on laptops,  so we reckon that Shockwave's ability to interface with the various  graphics cards might be the reason why it's not getting the image  property of a 3D cast member.
    So here's what's actually happening:
    When you get to step 4 of the DV, after you've drawn round the shape of your driveway, it tries to grab the image of a 3D cast member referred to by the  variable gWorldMember, and fails with the "four parameters expected" error message, on  this line of code...
          zoomAfterImage.copyPixels(gWorldMember.image, zoomAfterImage.rect, gWorldMember.image.rect)
    gWorldMember.image is being returned as <image:0> (not a usuable  image) and so its rect property does not exist, hence the crash.  This  line of code crashes whether or not there's a sprite of the relevant 3D  member on the stage at the time.  The member's defaultRect has been  temporarily changed so we can grab a 1024x1024 image off it.  Using  copyPixels, this image is resized down to the size of the zoomAfterImage  image variable (again 450x450).  This gives us an image at the original  size of 450x450, but with a softer image quality than if we'd grabbed  it from the 3D member at that size.
    Is anyone suffering similar problems or aware of what Adobe has been changing in the player?  At the moment I just don't see how I can fix this by changing my code...

    I had wondered if there was a clash between the Director 11.0 dcr and the Shockwave 11.5 player, so I downloaded the Director 11.5 trial and re-published it using that.
    It didn't make any difference, so I'm left with my original suspicion that Shockwave is failing to interface with certain graphics hardware setups via directX, when it tries to read the image property of a 3D cast member.

  • After Exchange 2010 SP3 and rollup 4 update conditional formatting causes messages not to appear in Outlook 2010

    Hi,
    after updating to exchange 2010 sp 3 from sp 2 and also updating to rollup 4, users who use conditional formatting cannot see new message unless they close and reopen Outlook.
    If you decide to change the font colour for unread messages, the messages do not appear in Outlook but a pop up indicates that a new message has arrived.
    If you reopen Outlook, the unread messasge appears.
    remove the conditional formatting and no issue with viewing unread messages as they arrive.
    running Outook version 14.0.7106.5003
    is this a known issue?  a user who never used conditional formatting will experience this right away.
    Thanks,
    rudif

    Hi rudif,
    If the issue only happens to users who use conditional formatting and OWA can work well for all mailbox, I think the issue should be in client side.
    Please try to reset View then set the conditional formatting back to have a try. If the issue continues, please try to recreate the Outlook profile to check whether the issue persists. Also try restarting Outlook in Safe mode by running
    Outlook /safe switch.
    Thanks,
    Winnie Liang
    TechNet Community Support

Maybe you are looking for