1/14/2014 Update is terrible/annoying

1/14/2014 Update is terrible/annoying
So we get this NEW update on 1/14/2014 it is build number 17.17
To say it is annoying is an understatment. No one asked for this update and the NEW annoying ads outweigh any small improvements.
1) When you push giude button the sides now have EMPTY wasted space. Taking away 25% of HD screen.
2) When you push giude button. There is a huge annoying Ad on the bottom. With the same Ad all the time. This new AD on add is uncalled for and takes away from the guide experience.
3) When you push giude button. You now see a Verizon Fios logo. Why do I need to know I am on Verizon Fios. I pay for the service and see your logo on my bill.
4) The new Tip of the day screensaver is annoying,but I can understand the motive behind it.
Instead of making your excisting boxes more annoying. Here is an idea. How about bringing out the new Media 6 turner box as promised many years ago
Thanks
PS I am sure there are more annoying features added to this build. That I will find at a latter date. Maybe some posters here can add them to this thread and maybe Fios will reverse this build.

The ads are enough for me to consider switching to Cablevision much as I don't like them. I pay lots of $$$ for my TV/Phone/Internet and they have the nerve to bombard me with ads?

Similar Messages

SharePoint Foundation 2013 - March 2014 Update Issue - Need help

We've just applied the SharePoint Foundation 2013 March 2014 Update, it always requires that we run the SharePoint Products Configuration Wizard at the end of install, but this time it's getting stuck at step 9 of 10 (the profile sync service cannot be
started even as admin). Is anyone else having any issues with this update? Has anyone else applied it yet? Is anyone else planning to apply it?
If anyone can help with advice on this I'd appreciate it.

Hi,
We can still access CA but sync will not start. Tried rebooting after the failed configuration and tried to run it again but it didn't work.
4/2014 10:45:16 5 ERR            Exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc
that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 127.0.0.1:32843
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
   at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
   at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken
userToken, Boolean appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String subscriptionName, String appSiteDomainId, Uri primaryUri)
   at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)
   at Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence.SPSiteExists(Guid siteId)
   at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.AddNextLevelObjects()
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
4/2014 10:45:16 5 ERR            An exception of type System.ServiceModel.EndpointNotFoundException was thrown. Additional exception information: There was no endpoint listening at
http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at //localhost:32843/SecurityTokenServiceApplication/securitytoken. that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException,
if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:32843
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
   at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
   at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken
userToken, Boolean appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String subscriptionName, String appSiteDomainId, Uri primaryUri)
   at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)
   at Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence.SPSiteExists(Guid siteId)
   at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.AddNextLevelObjects()
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
4/2014 10:45:16 1 ERR          One or more configuration tasks has failed or some tasks were not run
4/2014 10:45:16 1 INF          Leaving function TaskDriver.OnTaskDriverStopping
04/14/2014 10:45:16 1 INF        Leaving function TaskDriver.ExecuteTasks
04/14/2014 10:45:16 1 ERR        One or more configuration tasks has failed to execute
4/2014 10:45:16 1 ERR          Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review
the extended error information located at D:\Logs\PSCDiagnostics_4_14_2014_10_44_8_154_1605984328.log, fix the problem, and run this configuration wizard again.
04/14/2014 10:45:16 1 INF          Entering function StringResourceManager.GetResourceString
4/2014 10:45:16 1 INF      Leaving function TaskDriver.Run
04/14/2014 10:45:16 1 ERR      Post setup configuration was not run successfully when using the command line task driver module
04/14/2014 10:45:16 1 INF    Leaving function PsconfigCommandLineMain.Main
This is the meaty part of the errors we are getting. Right now our entire site is down. If you know of anything to remedy these errors let me know.

"Tearing" issues on CC 2014 update

All,
I'm experiencing the "tearing" issues with 4K files on the latest Adobe Premiere CC 2014 update. I'm using GPU acceleration on my system and it should be able to easily handle 4k footage with CUDA and OPEN CL. All files are .MP4 format UHD 3840x2160 100mbs shot on a GH4. All files were captured on a Sandisk Extreme Pro 16gb (95mbs class 10 SDHC I). I have confirmed that files themselves are NOT corrupt as playback on the GH4 shows clean files:
My system:
Windows 7 ultimate (64bit)
Gigabyte Ga z97x gaming 7 mobo (latest bios)
coolermaster CPU cooler
Intel core i7 4771 @3.5ghz
GeForce GTX 780ti (344.75 driver)
16GB corsair DDR3 ram
Samsung 1tb SSD system drive
corsair 7x750m PSU
So...my system is pretty darn "beefy" scoring a consistent 10,000+ score on 3DMark (93%)
A few notes:
I AM using an all SSD workflow (system OS and applications all on Samsung 1TB SSD)
Editing SSD is 500GB Western Digital (I have tried files on both SSDs....same issues)
I mention the SSD's because there are some folks that swear AGAINST them in editing etc....
I'm seeing this happen in the SOURCE window....MOST of the time it translates into the sequence after render. Whats weird is that sometimes the rendered sequence file will have "tearing" in completely different areas than the source file!
I have and AERO theme turned ON (as suggested in this forum)
Overall, I'm ready to throw in the towel with frustration. I'm reading about a lot of issues being reported with the latest CC 2014 update...with a lot of forum users saying that they are falling back to software rendering etc. The promise of Open CL computing and CUDA rendering of 6k files on an off the shelf laptop is escaping me ( A quick Peek at Adobe Premiere Pro CC 2014.1 (v8.1) - YouTube )
Here is what I am seeing:
HELP Adobe - I'm reading about so much of the same issues with this latest update!

Hi Rave,
Thank you for taking the time to reply. I found that simply deleting the ~/Library/Application Support/Adobe/AAMUpdater/ directory was a faster solution than taking the time out of my day to uninstall and reinstall all of my Adobe apps. I will be submitting a bug report to address the issue with the Creative Cloud updater.
Thanks,
dtderong

I'm unable to install the latest Photoshop CC 2014 update. Error message U44M1P34. Can anyone help please?

I'm unable to install the latest Photoshop CC 2014 update. Error message U44M1P34. Can anyone help please?

U44.. update error http://forums.adobe.com/thread/1289956 may help
-more U44.. discussion http://forums.adobe.com/thread/1275963
-http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
-http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html

PS CC (since JAN 2014 update) Layer-mask editing causes hangs/crashes

ONLY since JAN 2014 update, PS CC has been hanging/crashing when I paint/edit a layer mask. All may be well at first (or not), but suddenly the display of the mask (or mask overlay on the layer itself, as shown when hitting backslash key) is not shown in full but renders in s-l-o-w-l-y in rectilinear pieces <snapshot below was taken before video card upgraded but is still typical of what I mean>. When I view Windows' Task Manager for PS, I see my CPUs are each working at their upper limits (up to 80+-90+%), varying only by a few points, over a VERY long time... which could be MANY minutes. OR the System has decided PS is Not Responding.
In any case, whenever this happens, it means in all practicality PS CC is not working, so I either kill it or it's crashed.
Now, here's the thing: that VERY file, can immediately be opened in PS CS6 (which I have fortunately kept installed on my computer), and the mask will be as I thought it should be, and I can edit it as I always could, just fine! So it's obviously a PS CC thing, and I do NOT recall this happening prior to the JAN update. It is still a problem after the two subsequent updates.
I have not been able to determine the specific instances when this happens, as it seems to happen whenever I am editing a mask, no matter what size/softness/color brush, what magnification, what view mode, many or few layers, big or small file, etc.
I did upgrade my NVIDIA card (from GeForce GTX 260 [with current driver] to GTX660), just in case it was a factor (maybe kept it from crashing as fast? hard to tell... but it's still an unworkable problem). You can see from my Sys Info shown here from the PS CC Help menu that it should be more than sufficient for any PS CC task, and it's running the latest driver:
Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 4
Processor speed: 2664 MHz
Built-in memory: 16379 MB
Free memory: 12453 MB
Memory available to Photoshop: 14697 MB
Memory used by Photoshop: 60 %
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=1200, right=1920
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=1
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=2048
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
gpu[0].RendererID=4544
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.3221"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20131219000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=1.16816e+011
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]
I work on digital-photography files, and use a layer mask in almost every file, so this relatively-recent bug is a big PITA, having to switch back and forth between CS6 and CC!
Until there's a fix... is there a way to roll-back my PS CC version to BEFORE the JAN 15, 2014 update?

I am not qualified to comment on technical issues; I'm just a user whose son in IT is my 'technical support department.' (But he's not much of a PS user.)
I'm pretty sure, however, that all my Prefs were set to the same things BEFORE the Jan 16, 2014 PS CC update as after (unless the update itself changed something I was unaware of... the settings APPEARED to be the same but I can't easily locate my notes of what my Prefs were from long ago).
And they were the same as the PS CS6 I have had installed on this same system for a very long time, with older video card with older driver, with newer driver; newer video card with newest driver, etc. Yet after that CC update, CC has not (until this workaround) worked re 'the masking bug' for me, yet CS6 has always worked just the same.
So I conclude that the only variable (other than the video card upgrade I did in an attempt to solve this and of course those Windows auto-updates) in this scenario IS something to do with PS *CC*, and after Jan 16, 2014.
As for restarting the machine vs. restarting PS, well, PS is the major player of my system, so when I shut that (and LR) down, I might as well 'clean things up' by Restarting. BTW, I am in the habit of closing and reopening PS (CC or CS6) whenever I finish with a file and load another, in order to get back some of that memory which PS never seems to want to let go. (This is not new to the latest versions, I think. My son says it's a 'memory hog'? ;-) ) I track its memory use in Windows' Task Manager and find that seems to let it 'refresh' itself. (See, I told you I'm not a technical person. ;-) ) But I do not think this has anything to do with the bug. Just a quirk of PS. Like when a tool goes all wonky (for example, its little icon becomes just a 'plus' sign even though the tool is still performing correctly, it's telling me, I think, that it would like to be restarted. And that makes it feel all better... I mean, tool icon reappears.)
Anyway... it's up to Adobe to figure out IF and what may be wrong with PS CC -- it still doesn't work for me as I had it configured at first, and I think it should, right? -- and to fix that... PLEASE. SOON.

After updating to new 2014 updates Lightroom would not go from 'library' to Develop - screen was greyed out with the message saying:- Please renew your membership to reinstate the develop module. My membership is up to date. I then uninstalls Lightroom an

After updating from CC to new 2014 updates Lightroom would not go from 'Library' to 'Develop' - develop screen was greyed out showing the message 'Develop module is disabled. Please renew your membership to reactivate the Develop module.' Since my membership is fully up to date. I then uninstalled Lightroom 5 and then installed it again. Now when I try to open Lightroom 5 its LOGO flashes onto the screen and then 'crashes' in an instant. Please fix.

Hi brooks45,
Please try the steps mentioned in the KB Doc : http://helpx.adobe.com/lightroom/kb/unable-launch-lightroom-55.html
Regards,
Rave

After Photoshop CC 2014 update - Photoshop is very slow (Windows 7)

After updating today to the latest photoshop cc2014 Version, Photoshop starts very slow and is not useable.
I updated from V. 2014.1.0 to 2014.2.1 20141014.r.257.
Starting Photoshop Needs 6 minutes (before 1.5 minutes). The menue and button reactiontime is more than slow, you cant work with this Setup.
Is there a Problem with the new release?
And please Adobe, dont tell me, my System has a problem. Did only an update on the CC2014 Suite via creative cloud. Old PS Version (2014.1.0)runs great.
After testing a few time, I recovered my System back to Version 2014.1.0 with Windows recovery and Photoshop works good again.
So whats wrong with the new release?
My PC config:
Adobe Photoshop Version: 2014.2.1 20141014.r.257 2014/10/14:23:59:59 CL 987299 x64
Windows 7 64-Bit
Version: 6.1 Service Pack 1
Intel CPU-Familie:6, Modell:10, Stepping:5mit MMX, SSE (ganze Zahl), SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, Hyper-Threading
Physischer Prozessor: 8
Logischer Prozessor: 16
Prozessor-Taktfrequenz: 2664 MHz
Memory: 20463 MB
Thanks for any tipp!
BR.
Werner

The CC 2014 update 2014.2.1 is a month old and ACR 8.7 is two days old. Something strange is happening to you. First try resetting your Photoshop Preferences. This is a Adobe Photoshop User forum your not dealing with Adobe here. You seem to think you are and your attitude seems like you not open to to possibility that your system may have a problem. I think you may have one..
Adobe CC 2014 Product Updates/Downloads for Windows
Photoshop CC 2014
File Download
Size
Date
Notes
Adobe Photoshop 2014.2.1 Update for CC 2014 (64-bit)
249 MB
10/20/2014
Release 15.2.1
Adobe Photoshop 2014.2.1 Update for CC 2014 (32-bit)
223 MB
10/20/2014
Adobe Photoshop 2014.2.0 Update for CC 2014 (64-bit)
249 MB
10/6/2014
Release 15.2
Adobe Photoshop 2014.2.0 Update for CC 2014 (32-bit)
223 MB
10/6/2014
Adobe Photoshop 2014.1.0 Update for CC 2014 (64-bit)
236 MB
8/5/2014
Release 15.1
Adobe Photoshop 2014.1.0 Update for CC 2014 (32-bit)
210 MB
8/5/2014
Adobe Camera Raw – ACR
Adobe Camera Raw 8.7 Update for CC
122 MB
11/18/2014
Release 8.7
Adobe Camera Raw 8.6 Update for CC
106 MB
7/28/2014
Release 8.6
Adobe Camera Raw 8.5 Update for CC
100 MB
6/18/2014
Release 8.5

CC 2014 Updates on Mac- Remove Old CC Apps?

When I installed the CC 2014 Updates on my Mac, my old CC apps remained in place. How do I delete the older versions—simply drag their folders to the trash? Or is there another procedure for deleting them? After once going through hell with Adobe over licensing after I deleted a beta in the wrong fashion, I don't want to make any mistakes.
Thanks!

Yes, I would certainly want to know as well how to get rid of the CC version and why do we need to have both versions taking all that GB space anyway!
Thanks,

Photoshop CC (2014) Update "Waiting"

Photoshop CC (2014) update stays in "waiting" status as long as I care to let it remain like that.
Several hours ago I got the same message for both Photoshop and Bridge CC. I cancelled both and while the PS update cancelled successfully the Bridge update still (several hours later) says "canceling".

I should've updated this. I decided to reboot (Mac OS X Mavericks) and that resolved the problem. Thanks.

After December 2014 update, Compile Error - calling Excel Objects Sub "Object library invalid or contains references to object definitions that could not be found"

When try to call Sub in Excel Objects > SheetXX after the original xlsm is modified and saved by another user in diff machine, getting an error below and seems Excel cannot identify any subs exists in Sheet.
Compile error:
Object library invalid or contains references to object definitions that could not be found
Note: it seems that this problem has been occurring After December 2014 update and still exists even after applying the fix:
http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/11/forms-controls-stop-working-after-december-2014-updates-.aspx)

Hi Kwlee324,
Thanks for sharing the workaround with us. It would be very helpful for others who have the same issue.
Also I found a two useful links about the error message "Object library invalid or contains references to object definitions that could not be found":
https://support.microsoft.com/kb/2703186
http://blogs.msdn.com/b/vsod/archive/2009/06/05/visual-basic-6-controls-stop-working-after-security-advisory-960715.aspx
Hope it is helpful.
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

When trying to download a PS CC 2014 update, I get an error message stating: Unable to extract the downloaded file. Suggestions......

Any help with this problem?????

All Adobe CC 2014 Updates: The Direct Download Links for Windows | ProDesignTools
All Adobe CC 2014 Updates: The Direct Download Links for Mac OS | ProDesignTools

October 2014 update rollup for Windows Server 2012 R2 and Data Protection Manager 2012 R2

Hello all,
After installing the October 2014 update rollup for Windows Server 2012 R2 (KB2995388) on our Windows 2012 R2 Core Edition backup jobs of System State start to Fail, below the generic error:
The replica of Non VSS Datasource Writer on hostname.domain is inconsistent with the protected data source. All protection activities for this data source will fail until the replica is synchronized with consistency check.
The job was cancelled. The user either cancelled the job or modified the associated protection group.
Removing the update rollup all jobs complete without errors. Somebody is expiriencing the same issue? How can we resolve the problem?
Thnks, Andrea

Hi Andrea,
Have you installed the update 2919355?
To apply update 2995388, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2.
According to the official website, the issue which you described is not listed as the known issue.
Please uninstall this update and continue to monitor the official website for the latest news.
Best Regards.
Steven Lee
TechNet Community Support

Source and Program Monitor not working after October CC 2014 Update

I updated to the October 2014 Replace of Premiere Pro and since then I have had major issues with the Source and Program monitors.
I can select a clip from the media browser and have it appear in the source monitor - click play. The clip will play for a bit and the picture will stop, but the audio will keep going. After a few seconds the source monitor will just display a red screen and the audio will keep going. The same things happens in the program monitor (different clips that worked before the October 2014 update) will start displaying the yellow media pending screen - and then go to red after a few seconds. Again - this is a mutli-camera sequence that worked before the October 2014 update.
I am pretty much dead in the water at this point. And yes, I have rebooted, changed the Mercury play back engine from hardware to software. Nothing seems to correct the issue.

I have had similar problems. In fact playback is so sluggish it is unworkable.
In addition Audio in nested sequences doesn't play back, and when it does it is intermittent. Totally unworkable!

Computer hanging on "Save As" after latest CC 2014 update.

I'm using a Win 7 machine with a Intel Core i7 920 processor with 12 GBs of RAM. I use the latest updated versions of Lightroom, Photoshop and Bridge. Just here in the last few days when doing a "Save As" on a completed image in Photoshop halfway through typing the name of the saved file PS hangs. Cannot get out of it without a Control Alt Delete which is very frustrating after spending the time to do the edits and then getting to do them over again. Is anyone else having any problems like this. Probably not related but I have also noticed that my ColorEfexPro suite is running very slowly.

The CC 2014 update 2014.2.1 is a month old and ACR 8.7 is two days old. Something strange is happening to you. First try resetting your Photoshop Preferences. This is a Adobe Photoshop User forum your not dealing with Adobe here. You seem to think you are and your attitude seems like you not open to to possibility that your system may have a problem. I think you may have one..
Adobe CC 2014 Product Updates/Downloads for Windows
Photoshop CC 2014
File Download
Size
Date
Notes
Adobe Photoshop 2014.2.1 Update for CC 2014 (64-bit)
249 MB
10/20/2014
Release 15.2.1
Adobe Photoshop 2014.2.1 Update for CC 2014 (32-bit)
223 MB
10/20/2014
Adobe Photoshop 2014.2.0 Update for CC 2014 (64-bit)
249 MB
10/6/2014
Release 15.2
Adobe Photoshop 2014.2.0 Update for CC 2014 (32-bit)
223 MB
10/6/2014
Adobe Photoshop 2014.1.0 Update for CC 2014 (64-bit)
236 MB
8/5/2014
Release 15.1
Adobe Photoshop 2014.1.0 Update for CC 2014 (32-bit)
210 MB
8/5/2014
Adobe Camera Raw – ACR
Adobe Camera Raw 8.7 Update for CC
122 MB
11/18/2014
Release 8.7
Adobe Camera Raw 8.6 Update for CC
106 MB
7/28/2014
Release 8.6
Adobe Camera Raw 8.5 Update for CC
100 MB
6/18/2014
Release 8.5

Illustrator CC (2014) update failed

Have tried clicking the Retry button and restarting. Below is the exact error message.
Error message:
Installation failed
Installation encountered an error. Please restart your system and try again.(15)
More information
Exit Code: 15
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 0 error(s)

I had a lot of problems getting some of these 2014 updates to install. Most of the applications installed properly, but I had errors on both Photoshop and Illustrator CC and CC (2014). I also had a problem with Bridge, elements and InDesign. I finally rebooted my computer. I got failures again on all the same programs. Then I launched Photoshop CC (2014) just to see if it even worked. It did launch, but it immediately crashed. I also launched the failed installation of Illustrator CC (2014) and it did not crash. But after this, I initiated the updates again individually and each one installed without errors.
Photoshop CC (2014) now shows everything is up to date, but it still immediately crashes as soon as it finishes loading on launch.
Illustrator CC (2014) does not crash on load; I don't know about being active in it.
InDesign CC (2014 does not crash on load; I don't know about being active in it.
I don't know if this same "stab in the dark" method I used will work for you, but I thought I'd share it anyway. If it works, maybe reply here and tell us whether or not your Photoshop CC (2014) crashes or not.
Edit - Added Information: Normally, graphics driver updates do not help any problems I have ever had, but in this case, updating the driver for my graphics card has stopped Photoshop CC (2014) crashing.

1/14/2014 Update is terrible/annoying

Similar Messages

Maybe you are looking for