Create an Explorer script file that launches the desktop. Open Notepad and paste or type in the following text:
[Shell]
Command=2
IconFile=Explorer.exe,3
[Taskbar]
Command=ToggleDesktop
Save the file as showmydestkop.scf and put it in a location you’ll easily remember.
Launch Windows Task Scheduler. You can find Task Scheduler by using Windows 8's built-in search or by navigating to the Administrative Tools section of Control Panel.
Select Task Scheduler Library in the left window pane.
Right click in the task area and select Create New Task.
Enter a name (ex: ShowDesktop) on the General tab.
Set the task to trigger at log on by clicking new on the trigger tab, and selecting "At log on" from the Begin Task list.
Make your script an action by clicking New on the Action tab, selecting "Start a program" from the Action menu, and entering the full path of showmydesktop.scf (ex: C:\myscripts\showmydesktop.scf) in the Program/script field.
Toggle off "Stop if the computer switches to battery power" on the conditions tab. You want to log in to the desktop whether your notebook is plugged in or not.
Click Ok and close the Task Manager.
The next time you log in, whether at boot up or after log out, the desktop will launch shortly after the Metro screen loads.
Source of Information
EDIT: If you also want the classic XP start menu on the Desktop, install Classic Shell
Official answer (as per MS docs) to the general query "Can you access the Metro version of a non-default browser in Windows 8?"
Short answer: As per Microsoft's guidelines, only the default browser can access/participate in the "Metro style experience". So this behaviour is clearly intentional and unless Microsoft changes its guidelines or a browser-maker flouts them or some sort of hack is created, we're stuck with it.
The MSDN article titled White papers for Windows Store apps links to an interesting white paper titled Developing a Metro style enabled Desktop Browser that lists Microsoft's guidelines. Here's the document description:
In Windows 8, the browser that the user sets as the default for handling web pages and associated protocols may be designed to access both the Metro style experience as well as the traditional desktop experience. This type of browser is called a "Metro style enabled desktop browser." This white paper describes how to build such a browser.
Here are the interesting bits:
In Windows 8, the browser that the user sets as the default for handling webpages and associated protocols may be designed to access both new experiences as well as the traditional desktop experience.
...
New experience enabled desktop browser. A desktop browser that chooses to participate in the new experience when the user has expressed preference for the browser to do so. Such a browser can provide HTML5 rendering for webpages and service HTTP / HTTPS requests. By definition, such a browser has full access to Win32 APIs for rendering HTML5, including the ability to use multiple background processes, JIT compiling, and other distinctly browser-related functionality (like background downloading of files). Desktop browsers typically run at medium or low integrity level.
...
User experience framing. A new experience enabled desktop browser may participate in the new user experience only if it is the default browser. Desktop apps (typically packaged as .MSI, medium integrity level) run in the desktop. Windows Store apps (.appx packaged, run in App Containers, API set restricted to the Windows SDK for Windows Store apps, acquired via the Windows Store) run in the new experience. A new experience enabled desktop browser can be thought of as a desktop browser that can also participate in the new experience. The restriction to limit new user experience participation to the user's default browser is rooted in preserving the new user experience. Note that this limitation applies to all browsers, including Internet Explorer.
...
Tiles. If the default browser supports the new user experience, the browser's app tile (and secondary tiles, if they exist) will display in Start in a manner similar to Windows Store apps (as defined by properties that were specified in the .XML manifest that was copied during browser installation). Otherwise, the tile will appear as a desktop app. Verbs appropriate to the new user experience and desktop mode of the app will appear on the tile. ... The default new experience enabled desktop browser always appears as a square tile. Any secondary tiles belonging to the default new experience enabled desktop browser also appear with new user experience tile visuals.
...
Activation (launch). The following rules govern app activation:
Desktop shortcuts, pinned taskbar icons, and other "desktop artifacts" activate the new experience enabled desktop browser in the desktop.
Tiles in the Start screen activate the browser in the new user experience when the browser is the default. When the browser is not the default, tiles activate the browser in the desktop. This same behavior also applies to a browser's secondary tiles.
It is strongly recommended that browsers implement "contextual launching". This means taking the calling app's presentation (desktop or new user experience) into account when determining the browser's presentation (desktop or new user experience) for activations originating from other apps, such as when a user clicks an http:// link in their mail app.
Search contract activations always activate in the new user experience. These activations can only occur if the browser is the user's default.
...
We recommend that browsers provide a configurable setting to give users control over their preferred presentation experience. For example, a setting named "Choose how you open links", with options a) Always launch the new experience, b) Always launch in the desktop, c) Let the browser decide, aka contextual (suggested default).
...
Invocation into desktop presentation. If the new experience enabled desktop browser is not currently selected as the user's default browser, it can only launch in the desktop.
...
Windowing. A new experience enabled desktop browser, configured as the user's default, can choose to participate either in the new user experience or the desktop, but not both from the same running process.
Update (Possible workaround): Ok, someone needs to confirm that this works on their systems as well:
Suppose Firefox Nightly is set as the default browser. Go to Control Panel / Programs / Default Programs / Set Default Programs / (Firefox) Nightly / Choose defaults for this program:
Now uncheck Protocols like FTP, HTTP and HTTPS:
Now when you run IE (even though it's not the default), does the Metro version run?
Best Answer
Adding a Scheduled Task that launches explorer.exe on login is the method we're using for our automation clients.
This approach worked best for us as it doesn't require third party software or registry hacking, and we can deal with having an Explorer window on the desktop.