Extended confirmed users
6,677
edits
Windows Server 2008 build 4066: Difference between revisions
no edit summary
Someone200 (talk | contribs) (→Installation: but i installed this build and it formats the drive without any fails) Tag: 2017 source edit |
No edit summary |
||
| Line 13: | Line 13: | ||
}} | }} | ||
'''Windows Server 2008 build 4066''' is a pre-reset build of [[Windows Server 2008]], which was originally described by Grabberslasher in his [[UX.Unleaked]] blog entry on 1 May 2008 and was later uploaded to [[BetaArchive]] on 20 December 2008.<ref> https://www.betaarchive.com/forum/viewtopic.php?f=2&t=6768</ref> | '''Windows Server 2008 build 4066''' is a pre-reset build of [[Windows Server 2008]], which was originally described by Grabberslasher in his [[UX.Unleaked]] blog entry on 1 May 2008 and was later uploaded to [[BetaArchive]] on 20 December 2008.<ref>https://www.betaarchive.com/forum/viewtopic.php?f=2&t=6768</ref> | ||
It is the fourth and last available server build based on the pre-reset code, the others being [[Windows Server 2008 build 4028|builds 4028]], [[Windows Server 2008 build 4031|4031]] and [[Windows Server 2008 build 4038|4038]]. In a similar fashion to builds 4031 and 4038, this build uses the older i386 installation method. | It is the fourth and last available server build based on the pre-reset code, the others being [[Windows Server 2008 build 4028|builds 4028]], [[Windows Server 2008 build 4031|4031]] and [[Windows Server 2008 build 4038|4038]]. In a similar fashion to builds 4031 and 4038, this build uses the older i386 installation method. | ||
| Line 50: | Line 50: | ||
This is also the only available build able to render transparent notifications properly when DWM is enabled, as from build [[Windows Longhorn build 4074|4074]] onwards a black solid color background appears behind them. It is possible to get transparent notifications to work in builds ranging from [[Windows Longhorn build 4074|4074]] to [[Windows Longhorn build 4093 (main)|4093]] as well, but a modified <code>System.Windows.Explorer.dll</code> file is required. | This is also the only available build able to render transparent notifications properly when DWM is enabled, as from build [[Windows Longhorn build 4074|4074]] onwards a black solid color background appears behind them. It is possible to get transparent notifications to work in builds ranging from [[Windows Longhorn build 4074|4074]] to [[Windows Longhorn build 4093 (main)|4093]] as well, but a modified <code>System.Windows.Explorer.dll</code> file is required. | ||
Last but not least, it is possible to enable what is commonly referred to as "Aero | Last but not least, it is possible to enable what is commonly referred to as "Aero Stars" by setting up a <code>MILDesktop</code> DWORD, once again, like in build 4074. Disable the sidebar, unlock the taskbar and then merge the below values into the registry:<syntaxhighlight lang="registry"> | ||
Windows Registry Editor Version 5.00 | Windows Registry Editor Version 5.00 | ||
| Line 64: | Line 64: | ||
== Bugs and quirks == | == Bugs and quirks == | ||
=== SKU === | === SKU === | ||
This build's SKU oddly identifies itself in branding as Standard Server, while the true one being Enterprise Server. | This build's SKU oddly identifies itself in branding as Standard Server, while the true one being Enterprise Server. | ||
| Line 81: | Line 80: | ||
=== Windows Explorer === | === Windows Explorer === | ||
Windows Explorer ends up hanging and subsequently crashing pretty often in this build, most of the | Windows Explorer ends up hanging and subsequently crashing pretty often in this build, most of the time when navigating between folders. Should this happen, make sure to kill the <code>dw20.exe</code> process from the Task Manager and then proceed to restart <code>explorer.exe</code>. | ||
=== Sidebar === | === Sidebar === | ||
| Line 91: | Line 90: | ||
=== Installation === | === Installation === | ||
*On some computers and virtual machine configurations: | *On some computers and virtual machine configurations: | ||
** Setup might not be able to format the drive, | ** Setup might not be able to format the drive. If this happens, an "Unknown Hard Error" [[Blue screen of death|bugcheck]] will occur. | ||
**A <code>PAGE_FAULT_IN_NONPAGED_AREA</code> bugcheck might trigger after the first phase of the installation ends, thus the installation cannot continue. Reducing the virtual machine memory to 512 MB or less might solve the problem. | **A <code>PAGE_FAULT_IN_NONPAGED_AREA</code> bugcheck might trigger after the first phase of the installation ends, thus the installation cannot continue. Reducing the virtual machine memory to 512 MB or less might solve the problem. | ||
**The second phase of the installation can take a long time to complete and is extremely unstable. | **The second phase of the installation can take a long time to complete and is extremely unstable. | ||
| Line 106: | Line 105: | ||
*If upgrading to this build, you will need to ensure that <code>ialmnt5.sys</code> does not exist in <code>system32\drivers</code>. Leaving this file will cause a <code>REGISTRY_ERROR</code> bugcheck relating to this file, and rebooting will corrupt the registry, making it impossible to reboot back into setup. | *If upgrading to this build, you will need to ensure that <code>ialmnt5.sys</code> does not exist in <code>system32\drivers</code>. Leaving this file will cause a <code>REGISTRY_ERROR</code> bugcheck relating to this file, and rebooting will corrupt the registry, making it impossible to reboot back into setup. | ||
*On some machines, the user will get stuck at the login screen as the user is unable to press {{key press|Ctrl|Alt|Del}}. To fix this: | |||
*On some machines, | |||
#Boot into Safe Mode. | #Boot into Safe Mode. | ||
#Load up [[Task Manager]]. | #Load up [[Task Manager]]. | ||
| Line 118: | Line 116: | ||
*Logging in to this build may take several minutes after an upgrade. | *Logging in to this build may take several minutes after an upgrade. | ||
*There is a chance that setup could fail during an upgrade as <code>ntfs.sys</code> gets corrupted. | *There is a chance that setup could fail during an upgrade as <code>ntfs.sys</code> gets corrupted. | ||
=== Avalon Movie Maker === | === Avalon Movie Maker === | ||
This build does include the Avalon-based Movie Maker. However, it is not functional and opening it will result in multiple assertion errors. | |||
== Gallery == | == Gallery == | ||