My product expects msvcp71.dll to be present on the target windows machine, but unfortunately my customers didn't find this dll on the Vista machine due to which they cannot use my product. Customers can download this dll from net where it is is freely available, but I was looking for if it is possible to ship this dll along with my product. Register DLL file on Windows Server 2008 R2. Ask Question 21. (DLL or EXE) which is missing or not registered on this installation.
Marked as answer by System writer missing issue in windows server 2008 Thursday, April 26, 2018 8:34 AM; Friday, April 20, 2018 9:13 AM. “Windows could not start because the following file is missing or corrupt: system32 hal.dll. I can’t find the repair option on my product recovery DVD-ROM (Toshiba Qosmio F20). Windows Server 2008 is a server operating system produced by Microsoft.It was released to manufacturing on February 4, 2008, and reached general availability on February 27, 2008. It is the successor of Windows Server 2003, released nearly five years earlier.
Microsoft has added two years of optional extended support for Windows Server 2008 to its product-support roadmap.
Originally, Windows Server 2008 was supposed to move from free, mainstream support, to extended, paid support on July 9, 2013. It now will move from mainstream to extended support on January 15, 2015, Microsoft officials acknowledged last week.
Microsoft provides five years of mainstream support and five years of extended support for all of its Windows releases, whether they be 'consumer' or 'business.' Mainstream support is the period during which Microsoft provides free and regular updates including both security fixes and other patches for a product. Once a product exits the mainstream support phase, it enters Extended Support. During this period, security updates for a product remain free, but most other updates are only supplied on a paid basis, and require a separate Hotfix Agreement.
What's behind the latest change? Is Windows Server 2008 so popular that Microsoft decided to push back its end-of-life date for the product -- as has happened before in the case of Windows XP?
No, according to the Redmondian keepers of the lifecycle policies and procedures. From the latest edition of the company's quarterly lifecycle newsletter:
'The Microsoft policy provides a minimum of five years of Mainstream Support or two years of Mainstream Support after the successor product ships, whichever is longer..
'Modifications to the expiration dates for Windows Server 2008 are a result of the launch of Windows Server 2012, giving customers the additional 2 years of support.'
Microsoft released Windows Server 2008 to manufacturing in February 2008. It released its successor, Windows Server 2008 R2, to manufacturing in July 2009. And it released the most recent version of Windows Server, Windows Server 2012, to manufacturing on August 1, 2012.
And speaking of Windows XP support, Microsoft is continuing to remind customers that extended support for that product will finally end on April 8, 2014. There will be no security hotfixes for the product from Microsoft after that date.
'If Windows XP is still being run in your environment and you feel that migration will not be complete by April 8, 2014, or you haven't begun migration yet, Microsoft is eager to help. The impact it will have on your environment, the resources that are available to help you get your migration effort under way, and legacy support options should be discussed with your Technical Account Manager or Microsoft Account Representative,' the Softies reminded users in its latest support lifecycle quarterly e-mail blast.
Note: This is a VM on VMWare ESX server, but that should not matter
I put in the 2008 R2 x64 install dvd and can get to recovery, but it lists no Operating Systems. Clicking on Next brings me to
I start the command prompt, go to C: and perform a dir /a
Apart from files I put there myself, these are showing
Where to go next? Is it like the NTLDR problem with Windows 2003 where I can just drop a file in there and it will be hunky dory again?
Try BCDBoot.
Boot from the windows CD then go to the command prompt.
Type
SLYSLYI have had an immense amount of trouble getting windows to boot on a new 1TB disk. It booted off the new drive so long as the old drive was plugged in to the first SATA port, but after a year of running like that the old drive finally died.
I followed the advice of @SLY and @JFB and also this useful hint on how to access the Startup Repair function under Windows 2008 R2 Server from the command line. (x:sourcesrecoveryStartRep.exe)
After much trial and error I did get this machine to boot with only the new drive connected, so I can finally pull the aging OEM drive. As I don't really know exactly which step fixed it, I am just listing what I did below.
I had the same thing happen to me, here is what I did:
Fixed the problem, and now in msconfig (System Configuration) under the boot tab, I see all my Windows installations.
Corel painter lite serial number. It appears that there was a D: drive that can be accessed in recovery mode and the bootmgr file is there!
This got me going again. Not sure if the bootrec /rebuildbcd from Vick's answer was required, but that was already attempted before copying the bootmgr file.
Although this post is rather old, here is a solution for those who have this problem in the future.This procedure was tested and does work (at least in my case) :
You will need a Windows 7 x64 DVD.
Hope it helps
Try this:Type Bootrec /RebuildBcd while in repair mode, and then press ENTER.
if this will not work:
Restart the computer.
Based on this
You know why this fixed your problem?Because you have a recovery partition and obviously ignored it.You just needed to use diskpart and mark THE RECOVERY PARTITION (not Windows) as active.
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?