My 6th generation Ipod Classic will not eject, works fine otherwise and properly goes thru sync cycle. A message shows files are in use and device can't be ejected. If I close my internet browser it will eject properly every time.

Question

  I have a new HP Pavilion running Windows 7 with lots of memory and a terabyte of storage, using iTunes 11 with a 6th generation Ipod Classic.  Have used my current iPod for years with no problem until today; when I try to eject the device iTunes stops responding, there is a delay of about 10-15 seconds until a message box pops up: "the ipod cannot be ejected as there are files in use."  It also won't eject from the windows taskbar, same type of message appears. iTunes remains unresponsive until I click "ok" on the message box. I've reset the ipod twice and disabled the "enable disk use" button for the ipod -- with no change in symptom.
  I am not certain as to the fix but am 100% sure that the problem does not occur if I close my open browser; it occurs only when I have an Internet browser open.  I experimented with Google Chrome that I normally use, and also with Internet Explorer -- when either browser is being used the ipod cannot be ejected.
  I've used iTunes 11 for about 3-4 weeks and this problem had not occurred until today.

Answer 1

I have had similar issues with mine, happens mainly if I transfer songs and then decide to disconnect my iPod to listen to them with my IEMs (I use Interenet Explorer in my case and it is not neccessarely up when this happens, so I seriously doubt it is an issue conencted to the web browser). I have no patience for this so my trick is I try to eject it from iTunes, if that does not work, then I bring Windows explorer up, right mouse click on the iPod mounted drive and select Eject. It gives me the same warning but there is a third button selection called Continue. When I choose that it just disconnets the drive anyway and the iPod is finally disconnected. It seems to work each and every time I do it so this solution is fine for me. Would be intersting to see what the real root cause of this is because I started getting this problem with the newer iTunes 11.