Running Windows 7 Premium with UAC enabled and can run both 32 bit and 64 bit Bridge with no issues

By the way, so SSD drives on my system, just a bunch of regular SATA Drives. C: and D; same dive, Temp/Scratch drive on seperate volume

MK

Should have been more clear. My system Temp file is C:\TEMP, the Temp/Scratch being on a seperate volume is for Photoshop.

MK

digiscuro wrote:

 

When I temporarily changed the type of my user account to Administrator in Windows, Bridge still crashed on launch every time, it only runs when I launch it with my original admin account.

You do know that with UAC on the job, even if your user account is a member of the Administrators group, you're running everything WITHOUT Administrator privileges, right?

Frankly I don't know the specifics, but it sounds EXACTLY like a UAC / permissions issue, coupled with a failure inside Bridge to handle a failure due to denial of access.

Just a guess, but since most developers turn off UAC on their own systems for practical reasons, I'm thinking the exception handling code may just have never gotten tested.

-Noel

Ah, that's interesting information.  Is there anything special about the username of the one account vs. the other?  E.g., does one have a space in it while the other does not?

-Noel

Fixing and recreating the "Only run as Administrator" bug in Bridge CS6

I have been struggling with this bug for some time. First I tried reinstalling, changing permissions, etc, all to no avail. In desperation, I took digiscuro's hint and created a new admnistrator account on my computer, with precisely the same folder sharing permissions. Photoshop and Bridge cache location and scratch discs were also identical. Everything worked flawlessly!

After scratching my head, the only different configuration I could find was the location of the TEMP and TMP files as defined in Windows Environmental Variables. In my first account they were in E:\TEMP, a dedicated volume for temporary files. I like to use this configuration to reduce fragmentation on the system volume.

The new account placed TMP and TEMP at the default location, C:\Users\<user name>\AppData\Local\Temp. Next, I relocated the two files to E:\TEMP, using the Control Panel and rebooted.

And Bridge stopped working ! So it seems that the issue involves CS6 inability to find the system's temporary files, if they are not in their default locations.

My configuration: Windows 7 Pro 64-bit, Photoshop CS6 64bit, All programs on the first HD (C:\) and a dedicated partition (E:\) for temporary/scratch files at the beginning of the second HD.

Perhaps this may be of some help in solving the problem. We wait for a patch from Adobe.

Seems to me you lose most of the benefit of the SSD being very fast by not using it.  But the rules have only recently changed about whether an SSD can stand up to a lot of write activity, so it may make sense to limit the writes depending on the model you have.

For what it's worth, I saw a pretty significant performance increase just by having Photoshop use my SSD array for scratch.

-Noel

Apparently the problem lies in having the temp directory on C drive.  If anywhere else it fails.

From a Bridge post:

The issue is allways the same! For each CS6 Program (Indesign, Illustrator, Photoshop, Bridge, MiniBridge) and it occurs, when you change the Standard User Temp-Folder to another location than the standard setting

If you get back to standard all works fine.

Standard is

Temp=%USERPROFILE%\AppData\Local\Temp

and tmp=%USERPROFILE%\AppData\Local\Temp

But I hope Adobe will fix this behavior and make it possible to change the location of the User - Temp - Folder...

Thats a good tip Erik, thanks. As it happens I seem to be running okay now. I have installed a new Samsung 830 SSD and done a clean install of Windows and this time kept defult settings for temp files. I can now run all the CS6 programs fine, even when running in standard user mode.

You're welcome.

FYI, I have been running my Windows 7 system with UAC completely disabled since 2009, and before that I ran Vista the same way.  I recommend in my eBooks for both Windows 7 and 8 disabling UAC for the best overall computing experience, as well as instituting good computing practices (such as NOT trusting web sites by default) for avoiding malware.

As a software engineer, I know the internals, and I can say with conviction that UAC is no more than a badly implemented band-aid.  There are simply better ways for a conscientious user to protect his/her system from malware. 

People with UAC enabled still get malware infections, and I don't!

I'm not saying an application should require UAC to be disabled, that's really a design flaw in today's market, but just that running your system that way can net you fewer problems.

-Noel

Dragging that control panel slider all the way to the bottom disables UAC entirely, policy settings or no.

Keep in mind that the computer shop is most used to dealing with people who don't really know how to institute good computing practices - basically avoiding running everything in sight, installing every toolbar, and allowing every web page to "infect" Internet Explorer with Add-ons.

Configuring sites in the Internet Zone not to run ActiveX or allow installation of software is the key.  You may have to sometimes be willing to give up the "glitz" (fancy ActiveX-based functionality) some web sites provide, but you'll have the option to trust certain sites (e.g., your bank), and to use another browser (e.g., Safari) to see the "glitz" when you'd rather not trust a site.

Not surprisingly, if you follow good practices, back your practices up with safety nets like a good anti-malware solution and system backups, it's hard to go wrong.  I haven't had to rely on my anti-malware software (Avast!) as far back as I can remember.

Bear in mind that there are people who may be smarter and more experienced than the folks running the computer shop. I'm a 35 year career computer engineer who runs a software company now.  Note that I didn't say to disable UAC and happily continue doing everything as before.

I'd be miffed with the computer shop for assuming I was too irresponsible to run a Windows system conscientiously.

-Noel