I've found these related bug reports and code updates:
https://code.google.com/p/chromium/issues/detail?id=23911
http://codereview.chromium.org/257061
http://src.chromium.org/viewvc/chrome?view=rev&revision=28529

This bug is still active in the latest build: 5.0.322.2.
I guess this is an environment issue or an authority issue.
Could you please give us a solution to fix it well?

Thanks,

Could anybody have a look at this, please?

I have attached my screenshot. 
Please notice my env value, TMP and TEMP. It's NOT "C:", which is described in related 
bug.

	bug.png 78.6 KB   View   Download

I have two PCs and one has this problem and one does not.

There are a number of differences between the two PCs, but the one that is most
similar to the related bug (env value in root directory), is that the PC with this
problem, has had "My Documents" moved to a different disk drive than C: (using
Windows' built-in facility to move the My Documents folder).

I suspect that there is a small, but significant number of people who have C: drivers
or partitions that are running out of space, and so have moved My Documents to
another drive.

This bug is active in 5.0.339.0 dev build.

I have the newest 5.0.339.0 dev build too and I've come across this bug too, major 
bummer, but no biggie.

A temporary solution is that in your Windows enviroment variable setting, change the 
default value of "TMP" and "TMEP" to "C:\Temp" (make sure you have created a folder 
under C: directory).
Then, any extensions will be installed successfully without the current fail msg.

Problem does not exist in Beta version, it turns out, so it is a regression.

Now it is existing in 4.1 Beta ...

Still there in 5.0.342.2. I tried maowenbin's workaround, to no avail. It didn't help 
at all. I haven't done anything in particular with my environment variables (with the 
exception of PATH), so TEMP isn't at the root of my drive. There is enough space for 
temp files to be created (unless extensions recently started hitting 20GB+).

I'm using Windows 7 Ultimate x64.

Also have this problem.  Flashblock no longer works.  YUCK.  PLEASE FIX.

I see this problem on 4.1.249.1025 beta (40600).

My TEMP path is on C:, so it is not limited to cases where the temp path does not 
reside on C:.

@vostok4: The previous issue was with the TEMP at the root of the drive, not 
necessarily simply having it on C:. This issue happens regardless of where the TEMP 
folder is located in the dev builds (5.0).

If it helps the developers anything, I reinstalled Windows February 28th, and the dev 
build of Chrome followed shortly thereafter. That dev build did not have this issue. I 
first noticed this on March 8th. Should help narrow it down at least a bit.

I see this problem on 4.1.249.1026 beta, despite maowenbin's workaround.

whoever can fix this bug has my most esteemed respect!

I have this issue too, windows vista and chrome 5.0.342.5
I guess it's a OS issue, anyway I suggest a workaround: 

1- download the extension or the theme you want to install to your local hard drive. 
2- unpack it with 7zip, so you get a folder.
3- go to chrome extension tab or type chrome://extensions/ in chrome address bar.
4- click on the link that show you the developer mode extension tab and then load 
unpacket extension.

That should work.

Unfortunately that workaround is useless, because there is no way to download an 
extension - there is only the INSTALL button.

In between March 1st and today, this problem appeared in the BETA version, so it is 
part of some BETA update between march 1st and today.

LOL, kenstuart.mail have you ever tried to click the right button and select "save link 
as"?

In my WinXP machine, I usually have TMP=c:\tmp and TEMP=c:\temp and the extension 
install fails. It works if I change to TMP=TEMP=C:\Windows\Temp

Okay, but when I try to extract from the downloaded .crx files with 7zip, it says "not 
supported archive".

Try renaming it to .zip, I do that and I can extract it w/ WinRAR without issue.

Actually I tried the suggestion of Comment 21 and that worked fine and was a lot 
easier than the manual workaround.

In other words, I changed TMP and TEMP from:

C:\Documents and Settings\[username]\Local Settings\Temp

to:

C:\WINDOWS\Temp

and rebooted and now extensions install fine.

I'm having the same problem on both my Win7 x64 machines - one running 4.x and one 5.x. 
Since I already have a few extensions on each, it must have been something that changed 
recently that is causing this error to occur.

Btw, the .crx->.zip and install manually workaround definitely works.

I updated to 5.0.356.2 and still having problem with this. Did anyone solve?

(No comment was entered for this change.)

This browser is quickly becoming useless to me.  Is anyone looking into this issue, why 
it happens, or even working on a fix?  Running 5.0.342.8 beta

I think that what has happened is that the person who created the original issue, set 
the parameters (status, area, priority, etc) in such a way that it is not catching the 
attention of ANY CHROME employees, because it is set to a level below hundreds of other 
bugs.   And the guy who created the original issue has "left the building" (probably 
went back to ff).
Since the issue matches what people are experiencing, they post here rather than 
creating a new issue.   But what is needed is a new issue # that has the correct 
status, priority, etc.

I posted in this bug: https://code.google.com/p/chromium/issues/detail?id=23911 about three 
days ago and about two days ago its owner (tkent@chromium.org) added the label "Feature-
Extensions" to this bug. That may be a sign that some employee now knows about it. It also 
bumped us up if anyone is sorting the issues by 'last modified' (but we're now back to page 
3 and dropping).

I think the OP was not a Chrome employee and probably didn't have the ability to adjust the 
issue info. We could create a new issue, but it would only have the same effect as the 
latest modification once again.

What would help the most is more stars. I'm actually surprised there are so few.

I updated to 5.0.366.2 (dev) and still having problem with this. Did anyone solve?

@tkent, this issue looks like it might be a recurrence of 23911.  Can you take a look?

I can confirm that this issue is not related to temp variable folder path location 
neither permission.

Then why was the problem fixed when I changed temp variable folder path to 
C:\WINDOWS\Temp and rebooted ?

@kenstuart.mail: There are two seemingly unrelated bugs that cause the same error 
message. One being the TEMP issue, and another one causing the error message regardless 
of where your temp folder is. This bug started out by relating to the non-TEMP issue 
(afaik) and has since become the container for both bugs.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=43686 

------------------------------------------------------------------------
r43686 | tkent@chromium.org | 2010-04-05 18:51:43 -0700 (Mon, 05 Apr 2010) | 5 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?r1=43686&r2=43685

Make an error message verbose to investigate a un-reproducible bug.

BUG=35198
TEST=none
Review URL: http://codereview.chromium.org/1528018
------------------------------------------------------------------------

I'm not sure what is the root cause yet.  Anyway this should be related to TMP/TEMP.

People who have this issue,
Are you mapping a disk drive to another by fsutil/linkd/mklink?

Nope, I just have mapped network drives (regular mounted CIFS shares), nothing else.

Not for me too. I changed my TMP and TEMP in several different path but this no fix. 
Only one drive on my windows vista. 
tkent: Can I have a build with your verbose message? Anyway I can see by myself you 
only added a line to know where the tmp path is. I already know where is my tmp path: 
on the same drive, not the root, and anywhere I set my path I cannot create a directory 
for unzipping.
BTW, I can create dirs and unzip (ie with 7zip) with the same account running chrome, 
in the same tmp dir set in the path.
Can you suggest something else I can help you with?

Hmm, I still have no idea.
Could anyone try with the latest build and tell me an error message with a path name please?
http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/

I get:

"Could not create directory for unzipping:
C:\Users\MRUSIN~1\AppData\Local\Temp\scoped_dir318\TEMP_INSTALL"

I can confirm I can create that folder manually.

Also, my username is mrusiniak, it is being truncated to mrusin~.

My 2 cents

	chromium.png 219 KB   View   Download

the same problem.
The environment variables "TEMP" and "TMP" were changed.
The directory can be created manually without any Problem.

cheers.

	scr101.png 62.9 KB   View   Download

Installed snapshots/chromium-rel-xp/43726 on Windows XP Pro Version 2002 SP3 (gleened 
from System Properties control panel applet)

Error message attached when trying to install any extension.

I have tried changing TMP/TEMP and it doesn't make a difference.  Still busted.

QUESTIONS: are both "scope_dir????" and "TEMP_INSTALL" both supposed to be directories, one nested within the other?  If so is CreateDirectory() expected to 
create both nested, and is it supposed to do that?

	chromiumerror.png 6.4 KB   View   Download

Hi all,
Thank you for the feedbacks!
The path names and lengths seem good.

Could you try the following too please?
1. Invoke chrome.exe with additional flags:
  chrome.exe --enable-logging --log-level=0
  Either of stable/beta/dev/nightly is ok.
2. Reproduce the problem (try to install an extension, the dialog is shown, and press "OK")
3. Close Chrome
4. You'll have chrome_debug.log in Google¥Chrome¥User Data¥.  Please search chrome_debug.log for lines 
with "CreateDirecotry" or "Failed to create".  Please show such lines here.



> QUESTIONS: are both "scope_dir????" and "TEMP_INSTALL" both supposed to be directories,
> one nested within the other?  If so is CreateDirectory() expected to 
> create both nested, and is it supposed to do that?

Yes, both should be directories.  scoped_dir??? is created first [1], then tries to create TEMP_INSTALL and it 
fails [2].
[1] temp_dir_.CreateUniqueTempDir() in Start()
 http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/sandboxed_extension_unpa
cker.cc?revision=42146&view=markup
[2] file_util::CreateDirectory(temp_install_dir_) in Run()
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?
revision=43715&view=markup

Here is the line from my chrome_debug.log:

[4720:4148:82544715:ERROR:extension_error_reporter.cc(56)] Extension error: Could not 
create directory for unzipping: 
C:\Users\MRUSIN~1\AppData\Local\Temp\scoped_dir32257\TEMP_INSTALL

I've attached a copy of the file as well.

chrome_debug.log 3.0 KB   View   Download

and here - mine:

[3032:4520:628686093:ERROR:extension_error_reporter.cc(56)] Extension error: Could not 
create directory for unzipping: C:\TEMP\scoped_dir8365\TEMP_INSTALL

PS: I tried it with the latest nightly version of chrome, 43808 under WinXP.

chrome_debug.log 3.7 KB   View   Download

vostok4, yarick123, thank you.

It seems we can't get enough information from chrome_debug.log.
I expected it had errors of file_util::CreateDirectory()....

I'll add more logging code.

Could you try the instruction of Comment 48 with
  chrome.exe --enable-logging --log-level=0 --single-process
please?

I tried "chrome.exe --enable-logging --log-level=0 --single-process" with the build 
43814, the problem is gone !

The log file is attached.

PS: executing chrome, I had the next Message: "You are using an unsupported command-
line flag: --single-process. Stability and security will suffer."

Cheers.

the attachment for comment #53 was empty. I put it again.

chrome_debug.log 6.5 KB   View   Download

without option "--single-process" the Problem comes again

I tried "chrome.exe --enable-logging --log-level=0 --single-process" too, and then I 
had the same behaviour of yarick123: the problem disappeared.

To comment #53

Running with snapshots/chromium-rel-xp/43726 with:

--enable-logging --log-level=0 --single-process

The problem does not occur and extensions install fine.

	2010-04-07_1245.png 50.6 KB   View   Download

	2010-04-07_1247.png 61.4 KB   View   Download

Could this be the same as  issue 13044 ?  To those who can reproduce the bug: Does the 
issue go away if you set %TMP% to not be a path that includes a junction?

I don't believe this is the same problem. The Google Chrome exe is here:
C:\Users\<username>\AppData\Local\Google\Chrome\Application\chrome.exe

And my %tmp% and %temp% are both:
C:\Users\<username>\AppData\Local\Temp
(and I've tried changing this to C:\Temp without success)

I have two partitions on my drive (C: and D:), but these paths do not cross those 
boundaries.

I am using Windows 7. It may be relevant that I redirect 'My Documents', 'My Videos', 
etc. to 'D:\Documents', 'D:\Videos', etc., since that's the only boundary crossing that 
I'm aware of.

Also, the --single-process is the only workaround that's worked for me so far (I can 
install extensions with that option and then restart Chrome without it).

@skerner: My WinXP machine uses FAT32, so I think that  issue 13044  does not apply.

@tkent: when running Chrome 5.0.366.2 with "--enable-logging --log-level=0 --single-
process", the problem disappears:

[2228:3552:20639453:INFO:extension_unpacker.cc(147)] Installing extension 
C:\tmp\scoped_dir2084\extension_2_1_52.crx
...
[2228:2936:20688859:INFO:extensions_service.cc(604)] Sending EXTENSION_LOADED

I noticed that the install used a temp path that is in my %TMP% dir. In my machine, 
%TEMP% is set to "C:\temp", %TMP to "C:\tmp".

mshancock's comment about redirecting "My Documents" to D: made me think about my own 
situation. I recently (before encountering this bug for the first time) relocated my 
own document directories to E:, using the native XP tool to do so. (Right-click on My 
Documents, select Move, etc.)

The TMP/TEMP environment variable workaround had never fixed it for me in the past. 
However, playing a hunch, I set TEMP and TMP to "E:\Temp". Lo and behold, suddenly 
the problem disappears!  When trying the workaround in the past, I had set the temp 
variables to C:, as suggested.

Is it possible Chrome/Chromium is using a same-disk-only move function for the 
extension installation?  I know very little about Windows programming, but in Unix, 
there is a move function that will only work with a source and destination on the 
same partition.

To the others experiencing this bug: Try setting the TEMP and TMP variables to point 
to the same drive where your "My Documents" folder lives, and see if it suddenly 
works.  Make sure you create the new temp directory first, though.

I tried D:\Temp and it does not work for me.

@renbear: good thinking anyways. It does seem like partitions may still be a root 
cause.

@everyone: does anyone have this problem who doesn't have a partitioned disk and/or 
something like My Documents on a different partition?

I don't have a partitioned disk, I have Win7 installed onto C:, and that's my only 
physical disk in this machine.

I have network drives mapped, but there is nothing OS specific residing there.

I can confirm that the "--single-process" flag fixed the issue!

Network mapped drives seems to be a commonality among many users reporting this error, 
including myself...

@skerner: This issue seems different from  Issue 13044  (root TMP) and  Issue 23911  (junction).  Probably 
sandbox-related issue.

Everyone,
Please do not add --single-process for daily use.  It is a dangerous option.

aa, cira, mpcomplete,
This seems a sandbox-related issue.  Could you take this over please?

Gentlemen, I uploaded a ProcMon log of all disk activities (in the ProcMon 1.1 format).
https://dl-web.dropbox.com/get/logfile.pml?w=71a50474

Hopefully it will help.

Btw.. and yes, --single-process fixes the problem

Not sure if this info will help, but:
I encountered this error on one PC (AMD processor—Athlon XP), but NOT on 2 other PCs 
(Intel processors—a P4 and a Core2duo). 
All run Windows XP SP3, all using Chrome 5.0.360.4
(The AMD and one of the Intel PCs also have mapped network drives)

--single-process fixes the issue on the AMD machine.

(No comment was entered for this change.)

I was able to manually install an unpacked extension using the above method of 
unzipping the crx. I could use the extensions until I restarted Chrome, at which point 
they were all gone again. 5.0.342.9

@skerner - Just FYI that traffic to related forum threads about this issue is on the 
rise. Is there an update on this issue?

Related forum threads:
http://www.google.com/support/forum/p/Chrome/thread?tid=046e8fc7469251e2&hl=en
http://www.google.com/support/forum/p/Chrome/thread?tid=0d1a95c2bbfa2be1&hl=en

Thanks!

@google-chrome-guide5: A solution for  issue 13044  is out for review:

  http://codereview.chromium.org/1582022/show

  The fact that --single-process makes this issue disappear makes me suspect that this issue is 
related, and the above fix has a good chance of solving it.  I will update this bug when the 
above fix is in, so that we can see if it solves this issue.

Sam

Thanks for the update!

I found that adding --no-sandbox to the command line, solve the problem and let me install 
extensions. Is it safe to have this command line parameter enabled? What I only found is 
that this option let chrome "Runs the renderer outside the sandbox" as described in 
http://src.chromium.org/svn/trunk/src/chrome/common/chrome_switches.cc 
btw I don't really know wath does it means.

@skerner - Is there an estimate on the timeline? I don't mean to bug again, but this is 
one of our top issues in the forum right now. The growing traffic to these threads is 
concerning.  

Thanks!

@jokerulez: As tkent said in Comment #65; "Everyone, Please do not add --single-process 
for daily use.  It is a dangerous option."

In my case the problem was that my temp-folder is on a FAT32-partition (ramdisk).
I temporary changed it to a folder on a NTFS-drive and cound install (without
problems) some extensions.
After installation i changed the temp-folder-location back to my ramdrive, everythink
was fine :)
my system: vista ultimate, chrome 4.1.249.1064

Perhaps this helps somebody.

I fully second comment 76: is it possible to know when this issue will be fixed ?
Thanks

100% reproducible for me, but only after re-installing Windows.  Could changing account 
name after that be a factor, since account storage is not at C:\Documents and 
Settings\<account name>\ ?

Hi all ! :)
I'm having the same problem... tried to reinstall Chrome, update, install beta 
version (5.xxx)... the same problem...
Tried to move temp folder, set the tmp and temp strings... it does not change... 
still can not install extensions or themes...

PS1: I'm running Chrome on XP Pro system (My documents, and Desktop moved to 
partition D)
PS2: The extensions and themes worked in the beginning, but after a wile having the 
same irritating problem as described above, and can not use extensions, and themes 
:(((((

please take this BUG seriously, until this BUG is resolved I can not use Chrome on my 
system... :(( -- uninstalling it :((

A recent change (r46078) has changed the location where extensions are unpacked.  If 
anyone seeing this bug can run a tip-of-tree build, can you see if the problem still 
exists?  I will update this bug when this change gets to the dev channel.

I just tried on:

5.0.396.0 (46370)

And I can confirm the issue still exists.

@vostok4: I see you gave a log before.  Some extra logging has been added since then.  
Can you give a log with --enable-logging --log-level=0 with the version you just ran?

What file system are you using for local drives?  NTFS, or something else?

Sam

Using NTFS for local drives, Win7 64bit here, I do have mapped network drives, but they  
do not contain any system folder (AppData, Temp, etc).

Log file attached, what is the significance of the second to last log line (logstamp 
[5912:7080:528831283:INFO:render_view_host.cc(1104)]?)

chrome_debug.log 4.8 KB   View   Download

Sam: link in comment#82 is 404...

@trudelle if you need a tip build of chromium, grab it here: 
http://build.chromium.org/buildbot/continuous/win/LATEST/

Everyone with this problem,
What product of security software such as anti-virus are you using?

@tkent,

On my work laptop and desktop, I use Sophos Antivirus. At home on my desktop I have 
nothing. I have disabled on-access scanning in SAV (pretty much the only memory-
resident scan) and it did not help.

@tkent

> What product of security software such as anti-virus are you using?

avast 4.8

Thanks.  It seems security products doesn't affect to this issue.

I did what comment 21 and 24 said and it worked to fix my problem.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=46468 

------------------------------------------------------------------------
r46468 | skerner@google.com | 2010-05-05 11:42:17 -0700 (Wed, 05 May 2010) | 6 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=46468&r2=46467

Add logging to undersand exactly where CreateDirectory() is failing for users.

BUG=35198
TEST=none

Review URL: http://codereview.chromium.org/1948005
------------------------------------------------------------------------

@vostok4: r46468 adds a bunch of logging in the code that creates a directory to 
unzip the extension.  A log from the next nightly build should give more useful 
information.

>Log file attached, what is the significance of the second to last log line 
>(logstamp [5912:7080:528831283:INFO:render_view_host.cc(1104)]?)

Chrome asked to provisionally load the extension file, and the renderer could not do 
so.  This caused the renderer to send a message to the browser, which was logged.  
Because the next line in the log indicates that the browser started unpacking the 
extension but could not create a directory, I don't believe it is related to the 
issue at hand.

@tkent Avira Antivir Personal v9.0

I'm using MS Security Essentials.  
Just tried installing extension in latest build (5.0.396.0 (46380)); same error, log
attached.

chrome_debug.log 3.4 KB   View   Download

@trudelle: Revision 46468 adds a bunch of logging.  If you can run top-of-tree, I 
would be interested in seeing the resulting log.  Tip of tree builds are here: 

http://build.chromium.org/buildbot/continuous/win/LATEST/

@skerner,

Done, hopefully this helps. Ran the latest build, r46567.

chrome_debug.log 9.1 KB   View   Download

Note: this issue isn't limited to Windows -- I'm seeing it on MAC OS (10.6.2), chrome 5.0.375.29 (the latest beta 
build).

	chrome_extension_failure.jpg 22.0 KB   View   Download

More info (unlikely to be helpful, but you never know...): 

- This chrome installation ALREADY HAS several extensions installed, but since a recent update in the past few 
weeks, I've been unable to install anything new

- Changing permissions to 777 (world-writable) on the containing directory (-TMP-) made no difference

- My environment has no values set for TMP or TEMP

- I *can* install "unpacked" extensions, but they don't survive a restart, so this is an unsatisfying workaround

@skerner: Here's my log of the same error using 6.0.398.0 (46567)

chrome_debug.log 6.8 KB   View   Download

I have changed my settings as Comment 21 and it works. WinXP SP3+Chrome 4.1.249.1064

In fact, before I changed values, system values TEMP and TMP were "c:\windows\temp", 
but user values TEMP and TMP were "c:\Documents and Settings\---". I just edited my 
user values.

May this help someone~

Same on Snow Leopard 10.6.3 x64
I was using Chrome until this morning without problems and suddenly, this afternoon, nothing is working well anymore.
I'm using the last development of Chrome and also the last Chromium (from 
http://build.chromium.org/buildbot/snapshots/chromium-rel-mac). Both have the same problem.
Chromium is the worst: every time I restart the browser, it looses all the extensions configuration.

-----

May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny mach-lookup com.apple.pasteboard.1
May  8 20:56:00: --- last message repeated 25 times ---
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /System/Library/Keyboard Layouts
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /System/Library/Input Methods
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Library/Keyboard Layouts
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Users/Tildo/Library/Keyboard Layouts
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Library/Input Methods
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Users/Tildo/Library/Input Methods
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny mach-lookup com.apple.pasteboard.1
May  8 20:56:00: --- last message repeated 2 times ---
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data 
/Users/Tildo/Library/Preferences/com.apple.HIToolbox.plist
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny mach-lookup com.apple.pasteboard.1
May  8 20:56:00: --- last message repeated 18 times ---
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /System/Library/Keyboard Layouts
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /System/Library/Input Methods
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Library/Keyboard Layouts
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Users/Tildo/Library/Keyboard Layouts
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Library/Input Methods
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny file-read-data /Users/Tildo/Library/Input Methods
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny mach-lookup com.apple.pasteboard.1
May  8 20:56:30: --- last message repeated 1 time ---
May  8 20:56:00 Snowlino sandboxd[1684]: Google Chrome He(1683) deny mach-lookup com.apple.tsm.uiserver
May  8 20:59:40 Snowlino sandboxd[1688]: Google Chrome He(1687) deny file-write* /Users/Tildo/Library/Application 
Support/Google/Chrome/Temp/scoped_dir_u9wyPC/CRX_INSTALL
May  8 20:59:40 Snowlino [0x0-0x13f13f].com.google.Chrome[1552]: [1552:519:3944527595695:ERROR:/b/slave/chrome-
official-mac/build/src/chrome/browser/extensions/extension_error_reporter.cc(56)] Extension error: Could not create directory for 
unzipping: /Users/Tildo/Library/Application Support/Google/Chrome/Temp/scoped_dir_u9wyPC/CRX_INSTALL

I've just checked to see if there were any surprise and...actually there is!!! I
installed some extensions without any problem. Good job (may I add "at last"?)
skerner and team!I'm running Chrome v. 5.0.396.0. 

I'm running the same version (Chrome 5.0.396.0) and I'm still having the problem. 
This same version used to work before. I don't know what changed on my O.S. that caused it. I didn't update my 
Mac recently and the only new software I have installed was from Adobe CS5 collection (trial).
Must be something external to Chrome.

Problem solved for me using ver 5.0.396.0 dev. Thanks!

I am also on 5.0.396.0 dev, but the issue still occurs.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=47032 

------------------------------------------------------------------------
r47032 | skerner@chromium.org | 2010-05-12 08:13:57 -0700 (Wed, 12 May 2010) | 10 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=47032&r2=47031
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_posix.cc?r1=47032&r2=47031
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_unittest.cc?r1=47032&r2=47031
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/utility_process_host.cc?r1=47032&r2=47031

Use realpath() to find the path to the extension unpack dir on posix systems.

Extensions are unpacked by a sandboxed utility process.  The sandbox forbids file access outside the directory the extension will be unpacked in.  If the path to that directory contains a symbolic link, then unpacking will fail because following the link will cause file system access outside the sandbox path.  Use realpath() to get a symlink free path to the directory where the extension will be unpacked.

A similar issue exists on windows, with junctions instead of symlinks.  This will be fixed in another change.

BUG=13044,35198
TEST=FileUtilTest.RealPath

Review URL: http://codereview.chromium.org/2001013
------------------------------------------------------------------------

I'd put another view on this.  I'm also experiencing this issue, fresh install from
google 10 mins ago, 4.1.249.1064 (45376).  When ran it through filemon it had shown
quite a few name collision during directory creation, e.g.

1271	23:50:42	chrome.exe:1276	CREATE	C:\Documents and Settings\hui\Local
Settings\Temp\scoped_dir31847	NAME COLLISION	Options: Create Directory  Access: All

Which according to MS, maps to 'Cannot create a file when that file already exists.'.
 Full log attached, from the moment 'install' was clicked till the popup.

Since others reports --single-process works, it would suggest a race condition from
two threads both trying to create the same file/dir, and that the one that failed
from name collision throws their toys at the cot.

Thanks for looking.  I would switch back to Firefox in the mean time.

Chrome plugin install filemon.LOG 396 KB   View   Download

Very interesting. In fact, I experienced something similar yet different: The crx file 
got downloaded to two locations, scoped_dir and my default download location; the 
extension never got installed though.
--single-process solved it for me, too.

I should add that I am using 6.0.401.1 (47018), which probably contains some recent 
commits from  issue 13044  that are not in the 4.x versions.

Status update:  I am able to reproduce this when a junction or symbolic link is in
the path to chrome's .config directory.  A patch to solve this is out for review:  

http://codereview.chromium.org/2088006

 Issue 45062  has been merged into this issue.

I am now seeing this issue on the newest "stable" build for Mac OS X 10.6.3 as well. The Chrome version is: 
5.0.375.55.

the same with me - the new version 5.0.375.55 under WinXP has the same problem:
"Could not create directory for unzipping: C:\TEMP\scoped_dir27322\TEMP_INSTALL"

I am able to reproduce this error on Windows 7 Ultimate 64-bit running 6.0.420.0 
(48510, TEMP environment variable is default. 

I suspect this may have something to do with non-Vista behavior of file_util...
In some cases, it seems that Chrome reverts to SHFile_Operation. What lead me to that 
was at first it looked to me like base/file_util_win.cc CreateDirectory was trying to 
assign a valut to  a pointer to an undeclared new_dir but far be it from me to think 
the chromium developers would make such an obvious mistake so I then directed my 
attention to the //TODO: comment from skerner regarding the extra logging in regard 
to this bug. I initially used the "--enable-logging --log-level=0 --single-process" 
command-line arguments and replicated the previously-reported behavior that 
installing an extension works with "--single-process." I then ran it again without "-
-single-process" and noticed that the extra logging messages were not in my debug 
log. A little further digging and saw such code as

 if (win_util::GetWinVersion() >= win_util::WINVERSION_VISTA)
      CreateDirectory(to_path);
    else
      ShellCopy(from_path, to_path, false);

which looks to me like for all versions other than Vista, the Shell versions of 
operations are invoked.

Attached are the debug logs I mentioned above.

chrome_debug-single-thread.log 10.8 KB   View   Download

chrome_debug.log 11.9 KB   View   Download

@scottvr, I am no coder, but surely the >= means that this statement applies to any 
Windows Version from Vista and upwards...

Reproduced this error in Windows XP SP3.  Error did NOT occur in Xubuntu 10.04, though.  
Extensions install fine on that OS, at least for me.

extensions were working under xp sp3 until today. setting tmp and temp to a short path, 
and using --single-process did not help. last chromium build also did not help.

I'm currently using 5.0.375.55 and --single-process allowed me to update extensions 
and install themes. (Yes, I only ran --single-process to do the updates. I also 
logged the process of just trying to (re-)install Nothing, but I can't see anything 
useful in the logs from this version.)

My Theme stopped working at approximately the first restart after the update to 
5.0.375.55, and I first noticed the "Could not create directory for unzipping" on two 
unrelated XP machines on about 7/4/2010 ( 
http://meta.stackoverflow.com/questions/38544/stack-overflow-notifier-chrome-
extension/45795#45795 ).

One machine does have My Documents on a network drive, but not the rest of my 
profile. The other is an isolated laptop with everything on C:.

@Fuzzball... yeah, some of my post was poorly worded, including me forgetting that 
windows 7 even exists allowing me to lazily describe the >= condition, which I 
realized after submitting.

@skerner et al.. perhaps the meat of my message (#117) wasn't clear for the misspoken 
pieces of it.. what i meant to be of potential use to you was to say that your extra 
debugging messages don't show up in debug logs in the windows build if version is < 
win_util::WINVERSION_VISTA, and that maybe you'd like to add verbose messages in the 
SHFileOperation equivalent. 

On 6.0.422.0 dev, OSX 10.6.3

Same issue here.  I also tried --single-process and --no-sandbox, no effect.  All I want is to be able to install 
Vimium.  :(

confirmed on recent daily build since 6.0.xxx

i have this problem..On 6.0.422.0 dev 
win xp..

6.0.422.0 dev win xp та же проблема

Just did a fresh install of WIN XP SP3 and ran into this issue. Changin TEMP/TMP variables did nothing. The only thing that got synced theme installed and ability to add extensions was to run in single-process. Chrome v. 5.0.375.55, WIN XP SP3

Just did a fresh install of WIN XP SP3 and ran into this issue. Changin TEMP/TMP variables did nothing. The only thing that got synced theme installed and ability to add extensions was to run in single-process. Chrome v. 5.0.375.55, WIN XP SP3

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=49337 

------------------------------------------------------------------------
r49337 | skerner@chromium.org | 2010-06-09 15:56:48 -0700 (Wed, 09 Jun 2010) | 6 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/data/valgrind/base_unittests.gtest_mac.txt?r1=49337&r2=49336
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=49337&r2=49336
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_posix.cc?r1=49337&r2=49336
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_unittest.cc?r1=49337&r2=49336
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=49337&r2=49336
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/sandboxed_extension_unpacker.cc?r1=49337&r2=49336
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/utility_process_host.cc?r1=49337&r2=49336

Give the extension unpacker process a junction/symlink free path to the unpack directory.

BUG=35198,13044
TEST=FileUtilTest.NormalizeFilePathBasic,FileUtilTest. NormalizeFilePathReparsePoints,FileUtilTest.NormalizeFilePathSymlinks

Review URL: http://codereview.chromium.org/2088006
------------------------------------------------------------------------

@skerner, not sure if that fix exists in the latest builds, but I just tried r49367 and r49368 and both still failed.

yeah, finally fixed on 6.0.431.0 (49340)  snow leopard.

but flash crashed ... @_@

 orz ...

r49340 does not work for me either, (Win7x64).

Same problem! 
Chrome 6.0.427.0 dev
Chromium 6.0.431.0 (49374) 
Snow Leopard.

@vostok4: r49337 fixed one cause of this issue: a reparse point or symlink in the path to the directory where extensions are unpacked.  Apparently there are others.  A change that adds logging inside the sandbox is out for review:

http://codereview.chromium.org/2714016/show

Once it lands I will ask for logs again, running chrome in two ways:

chrome.exe --enable-logging --log-level=0 --single-process
chrome.exe --enable-logging --log-level=0 

Sam

I've fixed one possible cause of this issue:

In windows, many anti-malware software will hook some file-handling APIs. This may cause some subtle confictions with chrome's sandbox mechnism. Using --single-process will disable the sandbox thus avoid the failure.

To fix this, we simply check the existence of the temp directory after calling CreateDirectory.

please try attached patch

issue35198.patch 928 bytes   View   Download

PS: this patch works for me on lastest 375.70 stable branch.

@leonzy #135 FYI I have two Windows XP SP3 machines experiencing this problem (as I have already reported).

The one that is a member of a domain and has a roaming user profile, with a network-based home directory (containing My Documents, etc, but the basic profile is copied to C:\Documents and Settings\UserName) does NOT have anti-virus software installed (it is a development machine, and I trust my self).

The other, not a member of a domain, with a local profile, has AVG 8.5 (I think -- whatever the latest free version is).

So unless I happen to have two separate causes, I don't think this is my issue.

@markehurd #137: thanks for your info

I suppose my patch will only solve one possible reason, and for me it works.

In your cases, does --single-process works for you? If yes, it may indicate that the problem is related to the Sandbox. Note google's official chrome has disabled "--single-process" switch, please use chromium instead.

> So unless I happen to have two separate causes, I don't think this is my issue.

@markehurd: There is definitely more than one issue causing this problem.  One of them was fixed by r49337.  If you run the latest daily build, do you still see the problem?

@leonzy #138 Yes, I realised that -- I suppose I was just warning it was unlikely to help me. Yes --single-process works as I documented above #121.

@skemer #139 I don't really want to run beta software on either of the afflicted machines. But if I did, where would I find the instructions to get the latest bits?

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=49703 

------------------------------------------------------------------------
r49703 | skerner@chromium.org | 2010-06-14 11:50:19 -0700 (Mon, 14 Jun 2010) | 8 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=49703&r2=49702
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=49703&r2=49702
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?r1=49703&r2=49702

If CreateDirectory() fails during extension unpacking, log the exact OS call that failed.

This change is designed to help understand  bug 35198 , which we can not reproduce locally.

BUG=35198
TEST=manual

Review URL: http://codereview.chromium.org/2714016
------------------------------------------------------------------------

r49703 adds logging to show why CreateDirectory() is failing inside the sandbox.  If you can run a build past this revision (such as the nightly builds starting tonight), please run and try to install an extension with the following two sets of options:

chrome.exe --enable-logging --log-level=0 --single-process
chrome.exe --enable-logging --log-level=0 

And attach the results to this bug.


@leonzy: Your patch removes a test for the result of GetLastError().  I would like to know what GetLastError() is returning on your machine, and the logging I added should show me.


@markehurd: Nightly snapshots of chromium are availiable here:
  http://build.chromium.org/buildbot/snapshots/

Error _without_ --single-process:
[2504:5676:433258269:ERROR:extension_error_reporter.cc(56)] Extension error: Could not create directory for unzipping: C:\Users\mrusiniak\AppData\Local\Chromium\User Data\Temp\scoped_dir_23393\CRX_INSTALL
Enter CreateDirectory: full_path = C:\Users\mrusiniak\AppData\Local\Chromium\User Data\Temp\scoped_dir_23393\CRX_INSTALL
::GetFileAttributes() returned 4294967295
::GetFileAttributes() failed.  GetLastError() = 2
About to call ::CreateDirectory() with full_path_str = C:\Users\mrusiniak\AppData\Local\Chromium\User Data\Temp\scoped_dir_23393\CRX_INSTALL
CreateDirectory() gave last error 5
GetFileAttributes() returned 8208
Is the path a directory: 1
Failed to create directory C:\Users\mrusiniak\AppData\Local\Chromium\User Data\Temp\scoped_dir_23393\CRX_INSTALL
GetLastError() for DirectoryExists() is 5

With --single-process it works. Both logs attached.

chrome_debug-single-process.log 13.3 KB   View   Download

chrome_debug.log 9.7 KB   View   Download

I haven't installed the latest build (too busy with work and other things at the moment) but I'd like to confirm that from my ProcessMonitor logging when I attempted to debug the error before the directory /does/ get created.

The second call to DirectoryExists in #144 looks like you've noted this, but I'm just making sure :-) Permission denied (5) is 'interesting'.

OK First thing for everyone to note is the daily Chromium mimimal_installer.exe installs separately to your existing Chrome install, at least as far as I can tell.

Error without --single-process:

Extension Install Failure
---------------------------
Could not create directory for unzipping: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\Documents and Settings\Mark\Local Settings\Application Data\Chromium\User Data\Temp\scoped_dir_22959\CRX_INSTALL
Enter CreateDirectory: full_path = \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\Documents and Settings\Mark\Local Settings\Application Data\Chromium\User Data\Temp\scoped_dir_22959\CRX_INSTALL
::GetFileAttributes() returned 4294967295
::GetFileAttributes() failed.  GetLastError() = 5
Failed to create one of the parent directories: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\Documents and Settings\Mark\Local Settings\Application Data\Chromium\User Data\Temp\scoped_dir_22959

With --single-process I got a "Chrome has crashed. Do you want to restart?" (paraphrasing) followed by Microsoft's (Watson) Error Reporting -- you should be able to locate bucket 1917897661.

chrome_debug_failure.log 63.0 KB   View   Download

Failure_msgbox.txt 872 bytes   View   Download

chrome_debug_single_crash.log 36.2 KB   View   Download

Single_crash_EventLog.txt 150 bytes   View   Download

Re #146 That was for my local user on WinXP SP3 (not part of a domain) with a local Profile and My Documents.

At the time the message box was displayed the scoped_dir did not exist, and I wasn't monitoring the process with process monitor to tell you if it seemed to exist moments before.

Further to #146 -- both failures are repeatable (there's another fault stored at the same MS bucket for the --single-process crash).

This time I did run ProcMon at the same time for the without --single-process case. I've attached the csv of the partial ProcMon log that mentions scoped_dir in the path.

Note the entries "QueryOpen","C:\Device..."! I guess this means your debugging is stuffed (or possibly it is just a quirk of ProcMon, but given they all fail, I doubt it).

The other thing I noticed is there is no reference to CRX_INSTALL in the ProcMon logs (the whole log, not just the partial log included here). Is that because the MsgBox and log file are just using a general name (variable name perhaps) for the path that is, in this case, extension_0.crx?

chrome_debug_failure2.log 11.7 KB   View   Download

ProcMonLogfile_during_chrome_debug_failure2_mentioning_scoped_dir.CSV 12.3 KB   View   Download

One more thing Re #146 - #148 this for build 49919

my 50 cents on this one:
using latest build as of now (50031)
Take a look at the path it shows :)

One hint: i have volume C (that's where the path is pointing) actually sitting on a software mirror of 2 physical disks (done through standard windows logical disk manager)

"Impostazioni locali\Dati applicazioni" is the italian "Local Settings\Application Data"



Could not create directory for unzipping: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume2\Documents and Settings\Administrator\Impostazioni locali\Dati applicazioni\Chromium\User Data\Temp\scoped_dir_14529\CRX_INSTALL
Enter CreateDirectory: full_path = \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume2\Documents and Settings\Administrator\Impostazioni locali\Dati applicazioni\Chromium\User Data\Temp\scoped_dir_14529\CRX_INSTALL
::GetFileAttributes() returned 4294967295
::GetFileAttributes() failed.  GetLastError() = 5
Failed to create one of the parent directories: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume2\Documents and Settings\Administrator\Impostazioni locali\Dati applicazioni\Chromium\User Data\Temp\scoped_dir_14529

It seems all reports are failed with GetLastError()=5, which means ERROR_ACCESS_DENIED

Since we already know that chrome's sandbox does not intercept the CreateDirectory call, this failure must caused by some thirdparty security software.

my patch in #135 can possibly solve this problem, hope somebody with GetLastError()=5 can try it cause it works to me.

However there are some of us who get this error with NO AV or 3rd party software installed (as well as Windows Defender disabled).

I have the same bug. I've Windows XP-SP3 full updated & Chrome Dev 6.0.437.1 installed.
Files attached below

chrome_debug.log 86.3 KB   View   Download

chrome_debug_single-process.log 32.8 KB   View   Download

Win7 x64
Chrome dev 6.0.437.3
=================================================

chrome.exe --enable-logging --log-level=0

Fails with error in screenshot

in the directory "C:\Users\jay\AppData\Local\Google\Chrome\User Data\Temp" nothing is getting created at all, no scoped_dir_#####, and no scoped_dir_####/CRX_ etc



TMP/TEMP directories are not being used, although it does put them in the log I don't see how any of it has anything to do because it's all in appdata/chrome

=================================================

Installing extensions (for me) works with:

chrome.exe --no-sandbox

not sure if that's safe so after I install extensions I restart chrome


==================================================

Message me if your a dev and your working on this, I'll be willing to do however many tests you need.  As for me it's working without sandbox for now so I'm good! :P

chrome-dev.log 2.1 KB   View   Download

	2010-06-18_233223.png 25.0 KB   View   Download

i have this problme with 'could not create directory' and i've read through the comments above but i don't understand all this computer lingo. is there anyway of fixing this extention problem? (in layman's terms please) 

Hi all,

I'm the n00b that originally opened this bug in February... and I miss my extensions :(

Running Chrome 6.0.437.3 dev on WinXP x64, I tried running with the sandbox disabled ("chrome.exe --no-sandbox") and received the original error message (see original post).

Please let me know if I can help diagnose the problem.

I've tested the build 50702 and the single-process test, which now fails with a simple msgbox, not the one with extended debugging, confirms you're trying to create the folder "C:\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\Documents and Settings\Mark\Local Settings\Application Data\Chromium\User Data\Temp\scoped_dir_454\CRX_INSTALL" (sic) and succeeding. (This folder remains after the single-process Chromium closes.)

Logs attached.

chrome_debug failure.log 9.3 KB   View   Download

Chromium failure msgbox.txt 872 bytes   View   Download

Chromium failure procmon Logfile.CSV 12.3 KB   View   Download

chrome_debug single failure.log 14.3 KB   View   Download

Chromium single failure msgbox.txt 178 bytes   View   Download

Chromium single failure procmon Logfile.CSV 13.0 KB   View   Download

Working on build 6.0.447.0 (50617) Windows 7 Ultimate 64-bit with no switches added to the shortcut. Good job guys :)

I just wanted to confirm the "original" bug with the logging and procmon logs. This is for Google Chrome version 5.0.375.70.

chrome_debug failure.log 164 KB   View   Download

Failure Logfile.CSV 15.7 KB   View   Download

chrome_debug single success.log 34.6 KB   View   Download

Single Success Logfile.CSV 51.6 KB   View   Download

@TheFuzzball2005 did you mean that 6.0.447.0(60617) works good for you? And do you have this issue with previous versions?

thank you

@leonzy Nope, about:version shows 6.0.447.0 (50617), taken from http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/50617/

I have the same problem on Windows 7 Professional, using chromium 6.0.450.0 (50869)

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=51231 

------------------------------------------------------------------------
r51231 | skerner@chromium.org | 2010-06-29 22:57:37 -0700 (Tue, 29 Jun 2010) | 14 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_posix.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_unittest.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir.h?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir_unittest.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/sandboxed_extension_unpacker.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/utility_process_host.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.cc?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.h?r1=51231&r2=51230
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?r1=51231&r2=51230

Loosen permission on extension temp dir when a flag is used.

 Issue 35198  can not be reproduced locally.  To enable users to do experiments, three command line flags are added to chrome:

-- issue35198 -crxdir-browser: Have the browser process create the directory in which the extension will be unzipped.

-- issue35198 -logging: Enable log messages from directory creation in the utility process to be moved to the browser process.

-- issue35198 -permission: Use the most permissive file permissions possible on the extension unpack directory.

BUG=35198
TEST=manual

Review URL: http://codereview.chromium.org/2802018
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=51238 

------------------------------------------------------------------------
r51238 | skerner@chromium.org | 2010-06-30 00:19:11 -0700 (Wed, 30 Jun 2010) | 17 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_posix.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_unittest.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir.h?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir_unittest.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/sandboxed_extension_unpacker.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/utility_process_host.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.cc?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.h?r1=51238&r2=51237
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?r1=51238&r2=51237

Revert 51231 - Loosen permission on extension temp dir when a flag is used.

 Issue 35198  can not be reproduced locally.  To enable users to do experiments, three command line flags are added to chrome:

-- issue35198 -crxdir-browser: Have the browser process create the directory in which the extension will be unzipped.

-- issue35198 -logging: Enable log messages from directory creation in the utility process to be moved to the browser process.

-- issue35198 -permission: Use the most permissive file permissions possible on the extension unpack directory.

BUG=35198
TEST=manual

Review URL: http://codereview.chromium.org/2802018

TBR=skerner@chromium.org
Review URL: http://codereview.chromium.org/2861039
------------------------------------------------------------------------

I've installed 51358 and you're still trying C:\Device\HarddiskDmVolumes\etc at some stage.

Failure -issue35198-logging Logfile.CSV 12.9 KB   View   Download

chrome_debug Failure -issue35198-logging with procmon log.log 9.8 KB   View   Download

Failure -issue35198-logging msgbox with procmon log.txt 869 bytes   View   Download

chrome_debug Failure -issue35198-logging --issue35198-permission.log 8.5 KB   View   Download

Failure -issue35198-logging --issue35198-permission Logfile.CSV 12.3 KB   View   Download

Failure -issue35198-logging --issue35198-permission msgbox.txt 869 bytes   View   Download

chrome_debug Failure -issue35198-logging --issue35198-crxdir-browser.log 8.4 KB   View   Download

Failure -issue35198-logging --issue35198-crxdir-browser Logfile.CSV 12.3 KB   View   Download

Failure -issue35198-logging --issue35198-crxdir-browser msgbox.txt 872 bytes   View   Download

i have same problem in 5.0.375.86 beta

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=51416 

------------------------------------------------------------------------
r51416 | skerner@chromium.org | 2010-07-01 13:24:09 -0700 (Thu, 01 Jul 2010) | 16 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_posix.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_unittest.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir.h?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/scoped_temp_dir_unittest.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/sandboxed_extension_unpacker.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/utility_process_host.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.cc?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.h?r1=51416&r2=51415
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?r1=51416&r2=51415

Loosen permission on extension temp dir when a flag is used.

 Issue 35198  can not be reproduced locally.  To enable users to do experiments, three command line flags are added to chrome:

-- issue35198 -crxdir-browser: Have the browser process create the directory in which the extension will be unzipped.

-- issue35198 -logging: Enable log messages from directory creation in the utility process to be moved to the browser process.

-- issue35198 -permission: Use the most permissive file permissions possible on the extension unpack directory.

BUG=35198
TEST=manual

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=51231

Review URL: http://codereview.chromium.org/2802018
------------------------------------------------------------------------

r51416 adds some command line options that should allow us to see if the failure of GetFileAttributes() is due to the sandbox blocking the call, or if the sandbox user does not have file system permissions.  

If you are able to run a build after r51416, I would like to see the logs when you install an extension, running chrome with the following command line options:

(#1) chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -permission

(#2) chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -crxdir-browser

I'm seeing this problem on Chrome for Mac 6.0.453.1 dev for Extensions and Themes. The last install that *did* work for me was this Japan World Cup Football theme, which I installed on 06/29: https://chrome.google.com/extensions/detail/jblhoibnoneeabnceoeeibcpjpiildci?hl=en

With the possibility of repeating something (haven't been following too closely lately), I am still getting this issue since my first comment in March. Still running the dev channel, I'm now up to 6.0.453.1 (can't tell what revision as it's not from SVN) and the error message is longer (I added the error defines for reference):

Could not create directory for unzipping:
C:\Users\Johan\AppData\Local\Google\Chrome\User 
Data\Temp\scoped_dir_21842\CRX_INSTALL
Enter CreateDirectory: full_path = 
C:\Users\Johan\AppData\Local\Google\Chrome\User 
Data\Temp\scoped_dir_21842\CRX_INSTALL
::GetFileAttributes() returned 4294967295
::GetFileAttributes() failed. GetLastError() = 2         (ERROR_FILE_NOT_FOUND)
About to call ::CreateDirectory() with full_path_str = 
C:\Users\Johan\AppData\Local\Google\Chrome\User 
Data\Temp\scoped_dir_21842\CRX_INSTALL
CreateDirectory() gave last error 5                      (ERROR_ACCESS_DENIED)
GetFileAttributes() returned 8208
Is the path a directory: 1
Failed to create directory 
C:\Users\Johan\AppData\Local\Google\Chrome\User 
Data\Temp\scoped_dir_21842\CRX_INSTALL
GetLastError() for DirectoryExists() is 5                (ERROR_ACCESS_DENIED)

Note that not even scoped_dir_21842 was created.

I had the same problem with Windows Server 2003 SP2 and the latest 6.0.453.1 portable from portableapps.com. My portable apps are installed on another drive that is mounted via a junction off the boot drive. The junction was causing the issue for me.

I used the Disk Management mmc and added another drive letter to the partition and I was able to install extensions.

This is now fixed for me in Chrome for Mac 6.0.458.1 dev (I could not install Extensions or Themes in Chrome for Mac 6.0.453.1 dev). Thanks!

I just install Chrome for Mac 6.0.458.1 dev and it DOESN'T solve this problem.
Running on last Snow Leopard.
I'm used to run Firefox dev versions and I never have a problem like this...what a disappointment!!

@johan.skold, @markehurd, @leonzy, @j.kazemier, @vostok4: Can someone who can reproduce this issue on windows try to run with the options specified in comment #169?  The switches should be in the dev channel by now, so you should be able to use them without downloading a build.

Windows 7 Enterprise 64 bit
Chrome 6.0.458.1 dev (Fresh install)
UAC off
TEMP=c:\temp
TMP=c:\temp

chrome_debug.log 6.2 KB   View   Download

debug.log 612 bytes   View   Download

@skerner: Let me know if you need anything other than the stuff below.

Windows 7 Ultimate x64
Chrome 6.0.458.1
UAC disabled in control panel, just as jgieske above

chrome_debug_permission.log was started with command-line:
  chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -permission

chrome_debug_crxdir-browser.log was started with command-line:
  chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -crxdir-browser

In both cases the extension attempted to install was "Pwdhash Chrome Port":
  https://chrome.google.com/extensions/detail/dnfmcfhnhnpoehjoommondmlmhdoonca

chrome_debug_permission.log 6.9 KB   View   Download

chrome_debug_crxdir-browser.log 6.9 KB   View   Download

I have this problem, how can I fix it?? I really like chrome, and because of this I'm using firefox

thank you for helping :)

As requested in #176, using build 52651.

52651 --issue35198-logging --issue35198-crxdir-browser msgbox.txt 872 bytes   View   Download

52651 --issue35198-logging --issue35198-crxdir-browser chrome_debug.log 11.0 KB   View   Download

52651 --issue35198-logging --issue35198-permission msgbox.txt 872 bytes   View   Download

52651 --issue35198-logging --issue35198-permission chrome_debug.log 10.1 KB   View   Download

i also have this problem when installing extensions
i use a ram disk for temp directory.

	error.png 114 KB   View   Download

im still having an issue/problem when i want to install the extension. im using mac osx 10.6.4 with google chrome 6.0.466.4 dev

Could not create directory for unzipping: /Users/fenris/Library/Application Support/Google/Chrome/Temp/scoped_dir_DvWVUC/CRX_INSTALL

	Screen shot 2010-07-22 at 12.16.43 AM.png 422 KB   View   Download

Same as above with Win7 x64 ultimate and 6.0.472.0 (Official Build 53024) dev

Running with --single-process just simplifies error message to "Cannot unzip file"

Sorry, also %USERPROFILE% (C:\Users\brammator) is a mounted NTFS volume (not the junction to another directory)

I just installed Chromium build 53314 and now I can install new extensions again.
I'm running Snow Leopard last version.

Same problem with 6.0.472.0 on Win7 x64.

Same problem with 6.0.472.14 on WinXP

just wanted to point out on my computers that have this problem the extension sync doesn't work either; However, if I use the --single-process flag both extension install and sync work.

Extension sync's failure is silent however and I am not shown the alert dialog about the inability to create directory for unzipping

Reiterating #189 That is the same behaviour I have also always seen since I reported this problem.

You can see the attempts when monitoring the process with ProcMon.

How do we vote this to Pri-1 since Pri-2 hasn't fixed it in 6 months?

Works with --single-process which is the only reason I'm still able to use Chrome. Any less tech savvy user will just go back to a different browser.

Problem solved in 6.0.472.14.

Problem still persists in 6.0.472.14.

Same error message exists. With and without --single-process

	2010-08-04 08h29_31.png 247 KB   View   Download

Confirming it still exists with 6.0.472.14.

sigh i still have this problem on 5.0.375.125 beta as of now was not able to install a single extension :( i have to os windows 98 on c: and windows xp on d: this issue should resolved very soon

@skerner

Win 7 Enterprise 32-Bit
Chrome 6.6.472.25 

Ok I am having this issue as well.  So I did what was requested in post 169.  

(#1) chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -permission

(#2) chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -crxdir-browser

and I added a third option

(#3) chrome.exe --no-sandbox --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -crxdir-browser

As long as I have the no-sandbox option I am able to install extensions.

Here are the log files.......I really hope this helps.  

chrome_debug-#1.log 106 KB   View   Download

chrome_debug-#2.log 31.9 KB   View   Download

chrome_debug-#3.log 39.3 KB   View   Download

Forgot one #4

(#4) chrome.exe --no-sandbox --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -permission

chrome_debug-#4.log 121 KB   View   Download

I'm running 6.0.472.25 dev

Running command #1 from #169 i get: http://screencast.com/t/ZGQxNmJhY
Running command #1 from #169 i get: http://screencast.com/t/YzlmMmZlYjA

Windows 7 x64 Ultimate. Upgraded from Windows 7 RC Build 7100 (if that has anything to do with it).

It does however work with problems on my MBP 15" 2.66 ghz running 10.6.4 with Chrome 5.0.375.125. 

Without problems obviously*

Shame because the dev tools look good

Confirming it still exists with 6.0.472.36.  This is f'in ridiculous.  A company as big as Google cannot get this resolved?  Seriously?

Very annoying(v. 6.0.472.36)!

Btw, does anybody understands the cause?

I guess it's back to Firefox for now since no one seems to be actively pursuing this, regardless of the assistance offered by users/3rd parties. That's a shame.

Yes this is ridiculous. They've been aware of a show stopping bug for months and months now and can't be bothered to fix it aparently.. Back to Firefox here aswell.. what a shame.

I just have this problem randomly. I used Chromium on my USB, and while it's on some computer, I can install extensions, however, on other computers, I SOMETIMES get this error, but sometimes it works just all right.

I get this this time using 7.0.502.0 (dev 57009)
Could not create directory for unzipping: F:\PortableApps\ChromiumPortable\Data\PROFILE\Temp\scoped_dir_{increasing 5-digit number}\CRX_INSTALL
While F:\PortableApps\ChromiumPortable\Data\PROFILE\Temp is an existing directory, I can create another directory inside it, and if I delete it, Chromium is able to recreate the "Temp" directory. It is strange that Chromium cannot create the scoped_dir_* directory. So strange. Now it works on another computer AGAIN.

I know that the method that I'm using probably would be considered unsupported here, but I hope that the information gleaned from it may still be useful. I am running 6.0.472.14, the current Dev Channel build packaged at PortableApps.com installed to a shared drive so that I can access the browser from any of the networked machines without needing to install the browser on each of them.  When I attempt to install the extensions normally, I get the slightly verbose error reported above that includes the full path ("Could not create directory for unzipping: \Device\LanmanRedirector\datastore\rlbrega\Chrome\Data\profile\Temp\scoped_dir_29010\CRX_INSTALL").  When I add the --single-process (or --no-sandbox) flag, I am warned about the stability, but then I only get the short version of the error which has no path ("Could not unzip extension").  Using the manual unpack and developer mode install method does install them fine and they survive a reboot, however.

Without the single process flag, the browser is unable to make the folder that it wants to unpack in (as evidenced by the fact that the folder doesn't exist when I go look for it afterward).  However with the --single-process flag, the folders do get created, but in a rather strange way.  Like I mentioned before, this is a portable install which is located at Z:\Chrome\, where Z:\ is always my network share.  The browser, only when in --single-process mode, has consistently created folders at Z:\Device\LanmanRedirector\datastore\rlbrega\Chrome\Data\profile\Temp\scoped_dir_#####\CRX_INSTALL.  The bit that seems strange to me is that \Device\LanmanRedirector\datastore\rlbrega is all just another way of talking about Z:\ and not something that should be appended to Z:\ (which is a Windows share located at \\datastore\rlbrega\).

If it helps, my TEMP and TMP are both on the C: (local) drive and are in the Local Settings folder of my user profile.  The system versions of those variables are set to C:\WINDOWS\<the respective variable name>.

I don't know if that will be helpful to anyone here, but it seems slightly different from what has been reported before so I hope that the extra information might set off some lightbulbs about the causes of this bug.

Also I ran the tests per posts 169 and 196 and am including the debug output as well as the copied text of the info boxes.

chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -permission
chrome.exe --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -crxdir-browser

Both returned the following information box (with different scoped_dir numbers):
Could not create directory for unzipping:
\Device\LanmanRedirector\datastore\rlbrega\Chrome\Data\profile\Temp\scoped_dir_1265\CRX_INSTALL
Enter CreateDirectory: full_path = \Device\LanmanRedirector\datastore\rlbrega\Chrome\Data\profile\Temp\scoped_dir_1265\CRX_INSTALL
::GetFileAttributes() returned 4294967295
::GetFileAttributes() failed.  GetLastError() = 5
Failed to create one of the parent directories:
\Device\LanmanRedirector\datastore\rlbrega\Chrome\Data\profile\Temp\scoped_dir_1265


chrome.exe --no-sandbox --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -permission

chrome.exe --no-sandbox --enable-logging --log-level=0 -- issue35198 -logging -- issue35198 -crxdir-browser

Both returned the same error that the --no-sandbox option gave without the additional flags.

chrome_debug_no1.log 83.7 KB   View   Download

chrome_debug_no2.log 79.9 KB   View   Download

chrome_debug_no3.log 5.2 KB   View   Download

chrome_debug_no4.log 5.7 KB   View   Download

please suggest me a solution to this 

why they haven't solved this problem  already?  it's been 2 versions since the bug appears, I think is time to find a solution
I'm running 6.0.472.53, it's been released today and it is still having the problem
thank you

Extension problemS. There is a 100% solution.
Courtesy in comment 18 and 21 this solutiopn works

Comment 18 by jokerulez, Mar 17, 2010

1- download the extension or the theme you want to install to your local hard drive by click the right button and select "save link as"?. 
2- unpack it with 7zip, so you get a folder or else try renaming it to .zip, I do that and I can extract it with WinRAR without issue.
3- go to chrome extension tab or type chrome://extensions/ in chrome address bar.
4- click on the link that show you the developer mode extension tab and then load 
unpacket extension.
5- you are done

This problem, of course, continues to persist in 7.0.503.0 dev.

Hmm... maybe it is coincidence, but I had a thought when reformatting.

My normal procedure is to immediately download Chrome, and get it installed on first boot. Upon first launch of Chrome, Windows normally asks to allow or deny the program from running. I allow it. After all my drivers are downloaded and installed, I disable UAC and restart. Every time I've done this, I'm unable to install extensions.

Today I noticed... "Hey, Windows sucks at everything... why wouldn't it suck at privileges when using UAC?"
Knowing this, I immediately turned UAC off on first boot, rebooted, and then installed Chrome. I'm able to install extensions again!

If anyone can recreate this, we've successfully found one of the problems with this everlasting problem.

(Copied from  Issue 23911 )

Following this, I set my UAC controls to "always notify", rebooted, and bam: When I restarted Chrome(7.0.503.0 dev), extensions now work. I didn't even have to reinstall or "Allow" something new.

That was an inspired piece of deduction, TewanDraYk -- I salute you! 

Thank you TewanDraYk! Your solution works with Chrome (7.0.503.0 dev).

Still a problem for me, been an issue for a while.  I have the problem is the current stable build 6.0.472.53 on win7 64-bit.  

In addition I have used the canary build and it still exists 7.0.514.0.  In this build I used the flags mentioned earlier and attached is the error message, saying essentially what everyone else says.

As an additional thought I set the permissions on both of these directories (the Chrome SXS temp and Chrome temp directory) to everyone with full control.  Still see the issue.

The --single-process does fix the problem and extensions install so it does seem like a sandboxing issue at least on my machine.

On the canary build this is what I used for flags: "C:\Users\Alex\AppData\Local\Google\Chrome SxS\Application\chrome.exe" -- issue35198 -crxdir-browser -- issue35198 -logging -- issue35198 -permission

UAC is off, after I post this I am going to attempt to turn UAC on and see if it allows it to work.  I will post if that is successful, though I normally run UAC off and will return it that way after the test.

	error.png 60.4 KB   View   Download

Okay so new report, with UAC on and the slider all the way up, it works. No UAC prompts, but everything works as expected.  Only with UAC off do I get the error messages.  I'm not sure if this helps at all.

Also as a clarification on my previous comment: the --single-process flag worked on the canary build, but the other flags still produced an error message.  I didn't want people to assume that the issue flags alone fixed it.

@skerner - Is there an update on this issue? I'm receiving inquiries from our international folks who are starting to see this reported in the international forums as well. 

Are you still looking for the information outlined in comment #169?

I have the same problem. I use two PC, 1 with Vista work ok, and other with WinXP and fail.
I can`t sincronized both computers, because the error appears.
Please give the solutions, thanks

 Issue 54501  has been merged into this issue.

I had been having this problem since February, and last week someone on this thread had an idea that (almost) worked for me:
https://code.google.com/p/chromium/issues/detail?id=23911

I turned UAC to notify but don't dim, restarted, but then had to provide permissions (Chrome would only start if ran as Administrator). To provide permissions, you just navigate to:
C:\Users\<your-username>\AppData\Local\Google\Chrome\Application\<chrome-version>
and it should ask you to provide them (just hit Yes).

And now after 7-8 months I have extensions back! Though, I do feel a bit like it's more of a tradeoff than a solution.

Note: some of my other programs needed me to do something similar (e.g., Dropbox).

This issue is actually more than one bug.  Some of them have been fixed.  I broke this bug into separate issues, so that someone looking at the current breakage doesn't need to go through all the discussion about issues that are already fixed.

1) TMP set to an unreasonable value.  This is  issue 23911 .  Fixed in chrome 5.

2) On all platforms, a symlink or junction is in the path to Temp.  This is fixed in Chrome 6.

3) On windows, there is no symlink or junction free path to the profile directory.  This is  issue 49530  .  You will get a different error message in this case in Chrome 6.

4) On mac os, the sandbox is blocking the creation of a directory.  This is  issue 54698  .  

5) On windows, logs show that the sandbox blocks a call to CreateDirectory() with ERROR_ACCESS_DENIED.  Running with --single-process makes the issue go away.  UAC may be involved.  See  issue 54707 .

If the issue you are seeing doesn't fit one of these case, let me know.


Anyone still seeing this issue on the mac (#4) should star  issue 54698 .  We can't reproduce it, and two people who could no longer have the problem.  Knowing if others are still seeing it would be helpful.


To those users still seeing this on windows, star  issue 54707 .  What is your UAC setting?  If you enable UAC, does that change the behavior you see?

Now seeing this on Windows 7, Chrome 6.0.472.55

Extension Installation Failure
---------------------------
Could not create directory for unzipping: E:0\Users\Edward\AppData\Local\Google\Chrome\User Data\Temp\scoped_dir_4179\CRX_INSTALL

I don't understand why it is trying to use "E:0" my Windows7 installation is on "s:"
my TEMP and TMP are "s:\users\edward\appdata\local\temp" Shouldn't that be "E:\0\.." anyway?

Chrome seems to have picked "E:0" at random and then created all the subdirectories
within that "Users\Edward\AppData\Local\Google\Chrome\" etc.

Have deleted "E:\0\" and subfolders, uninstalled and reinstalled chrome, and have the same error. 

Hmm, unfortunately the problem has resurfaced for me, but only after I cleared my browsing data with "everything". I'm going to turn on *cough* UAC and see if I'm able to install extensions again. If I am, I'll turn it off, test it then, and then clear my browsing data and test it once more. I'll post results here.

Results:

Able to install?
UAC off: No
-> UAC on, restart: Yes
-> UAC off, restart: No
-> UAC on, restart: Yes
-> Reset browsing data, UAC off, restart: No

Argh... I hate Windows so.

My PC isn't running out of disk space at all and I've made sure that any of the Google domains are trusted and still I get this unzipping error message.  Too bad since I hate the blue default border and white tabs... very hard on the eyes.

Comment 220  by skerner@chromium.org:
> 2) On all platforms, a symlink or junction is in the path to Temp.
> This is fixed in Chrome 6.

Unfortunately still exists on Chrome 7.0.517.0 (from PortableApps).

each time i try to install an extensions i get the error"could not create directory for unzipping"...

I have Google Chrome 6.0.472.55

Whenever I install any theme it displays a message like this-

Could not create directory for unzipping:
C:\Users\Cheema\AppData\Local\Google\Chrome\User 
Data\Temp\scoped_dir_16459\CRX_INSTALL


please look at it and tell me how to resolve this issue...

Problem.bmp 4.1 MB   Download

@ken.lui (225)
That's a problem with PortableApps.

I'm sorry but now this appears to be a finger pointing match then. http://portableapps.com/node/24892

Does this mean we are just crap out of luck because neither Chrome or PortableApps is "at fault"?

Still have the problem in chrome 6.0.472.62 for windows.

In chrome 5 I could install extensions, if the browser was started with the parameter '--single-process'. In the version 6 this workaround does not work :-/

P.S. I have not even been asked, if I would like to upgrade my chrome from version 5 to version 6 - it has just been done.

	scr167.png 11.4 KB   View   Download

@yarick123: This is  issue 49530 .  

Even previously installed extensions now no longer "work"

@skerner: actually, my home-directory is not "under a" EXTRA "mounted NTFS volume" - it is on the system boot partition. Or do you mean, that the issue is, that the home directory is on a "NTFS" partition?

Here are results of calling of mountvol:

C:\>mountvol
...
Possible values for VolumeName along with current mount points are:

    \\?\Volume{d08fc647-69ae-4ca1-8e03-79a1f8bbaba7}\
        D:\

    \\?\Volume{52ae52d2-3417-11dd-ae63-806d6172696f}\
        C:\

Same here, Chrome Version: 6047262

	bugrepor.png 174 KB   View   Download

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=60471

------------------------------------------------------------------------
r60471 | skerner@chromium.org | Fri Sep 24 08:39:39 PDT 2010

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util_win.cc?r1=60471&r2=60470&pathrev=60471
 M http://src.chromium.org/viewvc/chrome/trunk/src/base/file_util.h?r1=60471&r2=60470&pathrev=60471
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_unpacker.cc?r1=60471&r2=60470&pathrev=60471
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.cc?r1=60471&r2=60470&pathrev=60471
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.h?r1=60471&r2=60470&pathrev=60471
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/utility_process_host.cc?r1=60471&r2=60470&pathrev=60471

Remove logging for  issue 35198 .

Remove switch -- issue35198 -logging .

BUG=56664
TEST=Install an extension on all platforms.

Review URL: http://codereview.chromium.org/3427019
------------------------------------------------------------------------

6.0.472.63 and WinXP SP3.  Just installed Chrome for the first time, I get the same error.

Env vars:
%tmp% is set to D:\temp\_tmp
%temp% is set to D:\temp\_tmp

Error message for me is that it is trying to install extensions to D:\temp\\Chrome\ - notice how this is not actually my temp path, and there is a double backslash.

I would so love to use extensions....

A permutation of the same problem still exists

... in WinXP SP3 on Chrome 7.0.517.24 dev as of 2010-0930.

Where...

the error message previously was "Could not create directory for unzipping..." 

... the error message is NOW:

--------
[window] Extension Install Failure

Can not unpack extension.  To safely unpack an extension, there must be a path to your profile directory that starts with a drive letter and does not contain a junction, mount point, or symlink.  No such path exists for your profile.

[OK]

The result is the same:  Cannot install ANY extensions.

I'm not working on a mounted volume, which is a specific description in  issue 49530 .

I looked at that issue but it just doesn't apply.   On this system I have a vanilla C:\ installed system and the temp spaces are all in the default location (i.e. C:\Documents and Settings\user\etc)  There are no mapped volumes involved.

Possibly there is really ONE root bug causing the failure of any extensions to install with several related bugs which are masking the issue, and causing multiple symptoms?

I'm only speaking from my experience, but if I'm seeing a root problem of not being able to install extensions, and a bugfix is implemented (such as 54707, which may have needed to be done regardless) and the original problem still exists, then it's not fixed.  

There are several assumptions here... UAC is the cause (not true, exists on XP), mounted volumes the cause (not true in my case), environ variables the cause, etc.   Maybe look at the problem without any assumptions?

With 7.0.517.24 beta, my issues are all gone.

I'm still getting the attached when I try to install an extension.  I'm running 7.0.517.24.

I'm on a Windows 7/64 machine. 

Chrome is installed under C:\Users\%username%\AppData\Local\Google\Chrome\Application\chrome.exe

	chrome-error.jpg 119 KB   View   Download

@themadtux: That error message means you have  issue 49530 .

I'm getting this for all extensions.  I recently moved from Firefox to Chrome and this is a bit of a dealbreaker.

I'm getting it :

chrome 8.0.552.0 dev

xp sp3 french

	chrome.JPG 235 KB   View   Download

how does this issue increase his priority?
thank u :)

As described way back in comment #220, there are several bugs that result in a user seeing the message "could not create directory for unzipping" when they install an extension.  Here are the ones we know of:

1) TMP set to an unreasonable value.  This is  issue 23911 .  Fixed in chrome 5.

2) On all platforms, a symlink or junction is in the path to Temp or Chrome's profile directory.  This is fixed in Chrome 6.

3) On windows, there is no symlink or junction free path to the profile directory.  This is  issue 49530  .  You will get a different error message in this case in Chrome 6.  This issue only happens if you mount disks in an uncommon way.

4) On mac os, the sandbox is blocking the creation of a directory.  This is  issue 54698  .  The two people who reported it can no longer reproduce it.

5) On windows, logs show that the sandbox blocks a call to CreateDirectory() with ERROR_ACCESS_DENIED.  Running with --single-process makes the issue go away.  This is  issue 54707 .  Fixed in the most recent builds of Chrome 7.

If the issue you are seeing doesn't fit one of these case, please file a new issue.

Adding to this issue slows down the process of fixing the bug, because the engineers who looks at it have to read 250 comments on  unrelated bugs that happen to give the same error message.  I restricted comments on this issue.  Please move the discussion to the issues listed above.

  If you are on the windows stable channel, wait for Chrome 7, which includes a fix  issue 54707 .  If you are seeing this on a mac, please comment on  issue 54698 , and help us figure out how to reproduce.  

 Issue 59937  has been merged into this issue.

(No comment was entered for this change.)

(Old comment had the wrong issue number.  Removed it, added same comment with correct issue number)

We found another way to get this message:   issue 59162  involves FAT formated disks on XP.  This is fixed on trunk.

At this point, all bugs that produce the error message in the subject are fixed.  If you still see this issue with a version of chrome greater than 10.0.620.0, please file a new bug.

(No comment was entered for this change.)