Why does Lightroom CC fail to launch on two windows 7-64 machines?

I'm in the process od updating two Windows 7-64 machines from Lightroom 5.7 to CC. It asks if I want to let the program open and I give permission. It will stat loading and then just quits on both machines.

first try, http://helpx.adobe.com/photoshop/kb/cc-applications-crash-immediately-launch.html
if that doesn't help:
    Un-install Photoshop CC.
    Un-install Adobe CC.
    Go to: C:\Program Files (x86)\Common Files\Adobe and find SLCache and delete it.
    Go to: C:\ProgramData\Adobe and find SLStore and delete it.
    Restart.
    Install Adobe CC.
    Install Photoshop.
    Restart.

Similar Messages

Why does Lightroom not see my teathered camera in Windows 8?

When I teather my Nikon D300 in Lightroom 4, It seem as the Windows 8 operating systems takes over the function and Lightroom does not automatically open captured image. Instead, Windows' picture window appears. I have not been able to figure out how to override the windows function so that Lightroom opens the captured image. Need Help!!!

Where is that in the menu...couldn't locate it?
Sent via the Samsung Galaxy S™III, an AT&T 4G LTE smartphonessprengel <[email protected]> wrote:Re: Why does Lightroom not see my teathered camera in Windows 8?
created by ssprengel in Photoshop Lightroom - View the full discussion
Also make sure you have your camera set to Point-to-Point not Mass-Storage mode:
Menu/Wrench/USB/'M/P'
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5226836#5226836
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5226836#5226836
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5226836#5226836. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Lightroom by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Why does lightroom 2.7 keep making me import a folder?

Every time I sync my Nikon Transfer folder to import my new pictures that I just loaded from my camera, a folder that I have already imported is included in the import. This folder and its contents are already in there. And lightroom agrees by telling me that it didn't import that folder because it already exsists. Why does lightroom try to import that folder in the first place?

Beat,
I'm not sure what you mean by that. I thought the folders viewed in Explorer and in Lightroom were one and the same. I think I see what you are getting at though. Perhaps if you were to change the name via Lightroom, the metadata gets changed in a way that causes Lightroom to think it needs to re-import. I don't change the names from the auto-generated sub folder that Nikon Transfer creates - which is the date and time using all numerals.
I think I am just going to copy this sub folder to somewhere else, delete the original, re-import it and see what happens. I will might lose all my raw edits in the process, but I have already delivered the finished jpegs to my client.

Why does Lightroom install to 2.x folder instead of simply 2?

Why does Lightroom install to a different 2.x folder each time [such as 2.5, 2.6, 2.7]? Why not just install to the same Lightroom 2 folder?

M Behrens wrote:
I don't think you can run 2 .x versions side by side. the setup will uninstall the old version before installing the new 2.x verion. You can run the beta 3s side by side with a 2.x but Adobe allows for this.
You're right, this was a mistake on my side. I was misslead by the fact that my recent LR 2.7 upgrade did not remove the 2.6 folders entirely, but this was because I had an additional customized file in one of the subfolders.
Sorry for my confusion.
Beat

Why does lightroom not display photos ?

Hello,
all of a sudden lightroom tells me "no photo selected " when I try to open a folder.All the folders are visible but the photos cannot be displayed.I am using lightroom 4.1
The last editing was done less then 12 hours ago without any problems.
Your help would be much appreciated.
Thank you very much,
1journey

Thank you so much for your reply.I solved the problem after fretting over it for some time. A filter was not turned off and once I turned it off all was well. Live and learn.
Thank you kindly ,
nihonbashi
Date: Sun, 10 Nov 2013 08:54:35 -0800
From: [email protected]
To: [email protected]
Subject: why does lightroom not display photos ?
    Re: why does lightroom not display photos ?
    created by F. McLion in Photoshop Lightroom - View the full discussion
Does it show an image count on the folders in the folder panel?
What does show if you select a folder in library?
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5830261#5830261
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5830261#5830261
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5830261#5830261. In the Actions box on the right, click the Stop Email Notifications link.
           Start a new discussion in Photoshop Lightroom at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Why does captivate hang when it is closed in window 8.1 professional ? How is it solved?

Why does captivate hang when it is closed in window 8.1 professional ? How is it solved?

Hi,
Do you see the issue every time you close captivate or is it only in some scenarios? Does it show any error messages? What captivate version are you using (64 bit or 32 bit)? Can you provide some more information or screenshots which can help us reproduce the issue.
Tamish

HT1926 Why does Itunes installed on a Toshiba Satelite with windows 8 not recognize my Ipone or Ipad?

Why does Itunes installed on a Toshiba Satelite with windows 8 not recognize my Iphone or Ipad?

It's possible that charger damaged some part of the connection on the iPad. There's little metal contacts on that small silicon chip sticking out of the port and if something happens to one of those little contacts it can effect how it works.
You can try taking it into an apple store and have them look at it. If you'd only used 'official' stuff there'd probably be no question but once they know that the damage, potential damage, was caused by a third party device, then it may be up to the discretion of the manager what they do with it. Whether they replace it under warranty or decide that the warranty is void (I honestly don't know how strict they can be with the use of third party devices and how they may/may not work)

Why does audio stop when pavilion 23xi sleeps (using Windows 8)

why does audio stop when pavilion 23xi sleeps (using Windows 8)?

Hello again @st3lla,
I can understand the fear of messing up a computer when I first started seriously working on computers back in the early 90's I had to format and re-install my operating system twice a day for quite a while before I figured out a very important step (at least important for me), and that was after I made a change to my computer to restart it. This way if I messed something up I only had to undo one thing and not 50 because I went wild on it. lol
Anyways, do not be afraid of your computer all you need to do is learn that step, how to keep your personal items backed up and then of course how to re-install your computer back to factory and you can always start over with a fresh build.
On to your questions:
Q - What are the steps to ensure that all HP updates are done.
A - Simply review the HP Support document: Using HP Support Assistant (Windows 8) and it will guide you through the process.
Q - What are the steps to ensure that all Windows updates are done?
A - Simply review the Microsoft Support document: Windows Update: Frequently Asked Questions and again you will find answers to this question. (***Note: Do not worry if the document refers to Windows 8.1 it is only an upgraded version of Windows 8 and the steps are the same)
I am also including a Windows Support document: Install the latest Windows 8.1 Update, which will guide you through how to install the Windows 8.1 update on your computer.
And finally, to put your mind at ease I am providing you with two important HP Support documents: Backing Up Your Files (Windows 8), and Performing an HP System Recovery (Windows 8), which will provide you with all the instructions you need to backup your personal files so you do not loose them if you ever do mess up the computer, as well as provide you with instructions on how to put your computer back to how it came from the factory.
Please re-post if you require additional support. Thank you once again for your post on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
Michael

Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings..

Why does Lightroom 4.3 use very high cpu when waiting for user to click OK?

I saved metadata for 52 photos.
Lightroom 4.3 couldn't save metadata for 2 of the photos and opened a window to tell me so. (It had no problem saving metadata on second attempt.)
While it waited for my response and wasn't doing any work, it was using over 50% of my CPU.
Why?
Windows 7 is 32-bit Professional.
Processor: Intel Core i5 750 Processor 2.66 GHz
Here's my system info as reported by Lightroom.
Lightroom version: 4.3 [865747]
Operating system: Windows 7 Business Edition
Version: 6.1 [7601]
Application architecture: x86
System architecture: x86
Logical processor count: 4
Processor speed: 2.7 GHz
Built-in memory: 3579.4 MB
Real memory available to Lightroom: 716.8 MB
Real memory used by Lightroom: 710.9 MB (99.1%)
Virtual memory used by Lightroom: 847.9 MB
Memory cache size: 2.0 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
Library Path: D:\Users\Calvin\Pictures\My Lightroom\lightroom\lightroom4\lightroom4.lrcat
Settings Folder: C:\Users\Calvin\AppData\Roaming\Adobe\Lightroom
Adapter #1: Vendor : 10de
    Device : 640
    Subsystem : c9593842
    Revision : a1
    Video Memory : 1007
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 8192
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 8192,8192
GL_RED_BITS: 8
GL_RENDERER: GeForce 9500 GT/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 3.30 NVIDIA via Cg compiler
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 3.3.0
OGLEnabled: true
OGLPresent: true
GL_EXTENSIONS: GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

I don't think so.
I have enough experience with LR to know what to expect for various activities.
Previews for all photos had been rendered long before I initiated the Save Metadata.
Metadata for 50 of the 52 files had already been written.
The high cpu had gone on for at least 5 minutes.   I switched to another app imediately after initiating the Save Metadata for the 52 files and only went back to LR when I heard my CPU fan running for a long time.
When I got back to LR, I saw the "Could not save metadata" window. I clicked "Show in Library" and OK. As soon as I did that, CPU usage went back to normal.
I've experienced the exact same scenario, where LR can't save metadata for all photos and I've never had LR get stuck consuming a very large amount of CPU.
As a test, I selected 118 other photos, changed metadata for all of them and then selected all and saved metadata. LR took about 20 seconds to save metadata for all 118 and LR CPU usage never went above 17%. The difference is that LR did not show the "Could not save metadata" window.

Why does "enclosing folder" not work from the SEARCH window?

I do a command+F search.
Command+2 to view as list rather than groups
and then sort by date modified.
When I find the file/folder I want I'd really like to do a command+[up arrow] which in the GO menu is a valid command.
Why does this work in finder windows but not in the search window?
I'm not using spotlight, just the good old command+F
This used to work in Sherlock 1 [using command+E] and when you opened the enclosing window, the file was already hi-lighted, faster to locate and saved mousing.

You'll note that in the Go menu that command is grayed out meaning it's not active in the search results display.
If you upgrad to Leopard then you can go to the Finder's View menu and select "Show Path Bar." The full path to any selected item in the Finder's window will be displayed in a path bar in the lower portion of the window. You can then double-click on any displayed folder to open a window on that folder.

Why does my system freeze during reader install on windows 7

why does my windows 7 system freeze during adobe reader installition

Is is hard to say. It could be anything from a corrupt font, interference from virus protection, corruption due to a virus, hard disk directory problems, etc. Are you able to download the full installer? Did you have a previous version of Reader on your System? What version of Reader are you trying to install?
Generally, if you clean your system of previous versions and bad installs:
http://labs.adobe.com/downloads/acrobatcleaner.html
You can then install. Try using this installer:
http://get.adobe.com/reader/enterprise

Why does lightroom 3.3 delete files it 'fails' to move? and why does it fail?

I'm in the process of moving a bunch of images around between machines, so from a remote machine I copied 10gb or so of .cr2, .jpg and .thm files into a temporary holding location on a local sata drive. I then started an import on the machine from the temporary holding location to the location I wanted the files at (which is a drive different than the temporary location). Lightroom trundled along for quite a while. Then reported to me that it had failed to move some files (The list was ALL the files).
I went to look at the temporary holding location on the boot drive and all the files were gone. I looked at the location I tried to import them to, and they were in fact there. HOWEVER they were not added to the catalog in lightroom!

Greetings..
I'm not sure what you mean by "force LR to import..."
It all depends on your work flow, and how you use LR, not any forcing. For example, I use keywords and collections. I organize my photos in the _folders_ by the method I mentioned. Then use collections to make up my groupings and sorted images. As for importing, every photograph taken has at least the date taken in it, and LR import options have a lot of different ways to use that date to import them. I selected one that works for me, and then just have to select the MajorProject as the toplevel folder on the import destination. LR creates all of the underlying folders.
I then use the Move option, and LR will move all of my images from the source directory into the destination. Note: This will not work from a portable drive, due to LR not being allowed to delete images from portable disks. You'd have to use Copy, and delete the originals after you've seen them in their new home.
Just out of curiosity, is there any reason you renamed your files, or was that a byproduct of how you did it? I try not to rename my images, if possible. I know that having multiple images with the same name causes some problems with a few export modules (I updated one, and had to recreate my export collection. It took the first file by that name it found, which, of course, turned out not to be the correct image).
The key here of course, is to keyword your images. I now have several ways to search for images; those taken by date, by project, and of course by keywords.
Cheers!

Why does Lightroom 4.4 fail to read photos on import?

I insert an SDHC card into a card reader, LR starts, reads the photos and generates a preview so I can select which photos to import. I click on import and LR shows a progress bar that proceeds too quickly. When the progress bar completes LR informs me:
"The following files were not imported because they could not be read. (50)"
50 is the count of files that "could not be read".
1. LR read the files to generate the previews.
2. I can read the files with Explorer and copy them to folders.
3. I can then tell LR to add the folders that I copied to the files to and LR can read them just fine.
This behavior is consistent across multiple SD cards from different cameras with different formats of files (jpeg, nef, mov).
I am running Windows 7.1 64-bit with a quad core i7 and 12GB of memory.

Ok, thanks to all that offered their thoughts and feedback.
The issue was that somehow the directory for imports got set to Users - it was no longer My Pictures. So everyone that dismissed LR's error message ("cannot read files") was on the right track. It could read the files just fine but it couldn't write them. And of course, LR didn't and shouldn't have permissions to write into the Users directory.
If Adobe had issued a correct error message - can't write file to directory "users" then none of us would have wasted our time here. I apologize to all for not checking to verify that the destination directory was what I had last set it to. Also, if a full path had been provided with the error message then it would have been obvious what the problem was even if the message were wrong.
ssprengel got me on the right track. I was not going to run LR as administrator (that would have actually made the write to Users work but would have been bad) but I did go to change the destination directory and found that it was longer My Pictures.

Why does Lightroom no longer show up in Creative cloud as one of my apps?

I originally had a Lightroom 5 license but later signed up for the Creative Cloud Photographer's bundle. This has been working fine. However, following a recent update, I decided to check out the apps and find that Lightroom is not shown as an installed app although Photoshop CC (2014) and Bridge are. I am sure that Lightroom used to show up. I am concerned that I may miss out on any upgrades to Lightroom.

Does your Cloud subscription properly show on your account page?
If you have more than one email, are you sure you are using the correct Adobe ID?
https://www.adobe.com/account.html for subscriptions on your Adobe page
If yes
Some general information for a Cloud subscription
Cloud programs do not use serial numbers... you log in to your paid Cloud account to download & install & activate... you MAY need to log out of the Cloud and restart your computer and log back in to the Cloud for things to work
Log out of your Cloud account... Restart your computer... Log in to your paid Cloud account
-Sign in help http://helpx.adobe.com/x-productkb/policy-pricing/account-password-sign-faq.html
-http://helpx.adobe.com/creative-cloud/kb/sign-in-out-creative-cloud-desktop-app.html
-http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
-http://helpx.adobe.com/creative-suite/kb/trial--1-launch.html
If no
This is an open forum, not Adobe support... you need Adobe staff to help
Adobe contact information - http://helpx.adobe.com/contact.html
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us"

Why does Lightroom CC fail to launch on two windows 7-64 machines?

Similar Messages

Maybe you are looking for