Mysterious Local Disk (Q:) Drive Appeared


Recommended Posts

For those of you who are panicking wondering why a mysterious Local Disk (Q:) drive has suddenly appeared in your drive list, do not panic. After a lot of research, I discovered that Office 2010, specifically the Click-To-Run setup version, is what does this.

For those of you who don't use 2010, basically, the Click-To-Run beta mounts a drive called Q: in which it stores files it apperently needs to install Office 2010. It usually makes people panic because the user is denied permission when trying to open it, he/she is unable to reset the permissions of the drive and take ownership, and the drive does not show up in the device manager at all.

So yeah, just wanted to let you know, not sure if this has been posted before.

I run Office 2010 on my home machine and I've never seen a Q:\ drive before. I have several network drives that I frequent so I would have noticed one if it ever mysteriously appeared. Is this "Click-to-Run" a specialized verison, feature, or something else? Just curious.

I tried the Click-to-run beta in a VM the other day and went looking for this drive Q that people mention. Didn't see it.

Also, the CTR install and subsequent product set seemed less convenient than a traditional install. Ultimately it would've been faster to simply install everything at once rather than delay-load each app. It probably won't be used much, but it's nice to see Microsoft testing new delivery mechanisms.

Just read a small excerpt on the click to run installation so I see what I havent seen a Q: drive. I have the normal installation method. Its an interesting idea and nice to see Microsoft try something new but I prefer the normal installation method.

  • 2 weeks later...

Just read a small excerpt on the click to run installation so I see what I haven?t seen a Q: drive. I have the normal installation method. It?s an interesting idea and nice to see Microsoft try something new but I prefer the normal installation method.

Most folks do (either personal preference, or they are running an x64 flavor of Windows).

While the drag of C2R performance is generally within the margin of error (five percent or less vs. a traditional Office 2010 x32 install), Office 2010 *x64* is so much faster than 2010 x32 (while it's Excel 2010 x64 that really shines, performance gains in Word and Outlook are nothing to be sneezed at), I'm actually recommending the x64 flavor unless you have add-in/plug-in issues.

  • 4 weeks later...

I tried the Click-to-run beta in a VM the other day and went looking for this drive Q that people mention. Didn't see it.

Also, the CTR install and subsequent product set seemed less convenient than a traditional install. Ultimately it would've been faster to simply install everything at once rather than delay-load each app. It probably won't be used much, but it's nice to see Microsoft testing new delivery mechanisms.

C2R is aimed at thin-client and other optical-drive-constrained devices that can run Windows XP and later (including virtual machines), and is meant to be sold by cloud and SaaS (Software-as-a-Service) providers. (I was in the beta for both traditional and C2R and actually compared Word and Outlook of each heads-up.) The installer is small enough that it would fit on the now-retired 1.44 MB high-density floppy-disk (let alone thumbdrives, optical media, and the various forms of MemoryStick). The traditional install will likely remain with us for quite a while to come; C2R is meant as simply another install option.

Also, how many folks actually do what is often called the *kitchen-sink* (full) install of Office (any version)? I would give long odds that enterprises have many clients do installs that way (especially in terms of an over-network install; the preferred install within an enterprise seems to be install-on-first-use, and from a network drive); home users and those that connect via VPN seem to be the most likely to do a KSI (I've always installed Office that way on my personal systems, and have recommended that other home users do the same).

Agreed; it normally *is* faster to install everything at once (which is why I prefer doing full installs, and have going back to Office 97 Professional). The sticking point (until recently) with the full install has been the space it chews up on the boot partition (all versions of Office prefer to share the partition with whatever version of Windows is installed, and 2010 is no exception); however, the terabyte hard drive (and especially the *inexpensive* terabyte hard drive) has made that issue pretty much moot.

Thanks for this. I was worried when I saw the "Q" drive appear. I thought I had been hacked or something. Why don't Microsoft explain these things before frightening the life out of everyone.

It was explained by Microsoft (and myself, among other testers) in several posts on the Office 2010 beta newsgroups, and by me again here on Neowin (in a post in the Windows Beta forum).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • lots of people us facebook for stuff, threads though no
    • Can you read? I've said I'm willing to pay more for a notchless (no notch) 3:2 screen.
    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • make your own notch - it's not that hard
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      510
    2. 2
      +Edouard
      174
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Steven P.
      87
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!