- Windows Vista, 7, 8, 8.1, 10
- Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016
If you attempt to restore a Windows Server Backup or Windows Backup recovery image (system state) from a bootable recovery media (either DVD, USB or a recovery partition) you receive the following error message
Just to keep this simple. The limited amount of information available on-line on this error suggests that either the image is corrupt or you are having a network reliability issue.
These could be true. In my case, it wa the path length that I was using to recover the image from. I was recovering from
It turns out that the entire path must be 110 or fewer characters otherwise it will fail with the 0x80070001 error.
A simple fix is to temporarily create the path \\192.168.15.106\BackupFiles\WindowsImageBackup on your share and then copy the <hostname> folder into it. This worked in my case.
- Windows 2000, XP Professional, Vista Business, 7 Professional, 7 Enterprise, 8 Professional, 8 Enterprise, 8.1 Professional, 8.1 Enterprise, 10 Professional, 10 Enterprise
- Windows Server 2000, 2003, 2008, 2008 R2, 2012, 2012 R2, 2016
- Windows Scripting Host 5.8 or higher
It’s been a problem since 1999. You want to install a Startup or Shutdown Script on a local Windows machine without having to go through GPEdit.msc to manually populate the user interface necessary to install the script processing hook.
Well, now you can do it automatically!
So here is a VBScript api file which does the work for you to install either a Startup or Shutdown script from the command line. This installs the script as part of the Local Windows Group Policy processor, which on Domain Joined systems will be executed before Domain Logon Scripts.
- No warranty is offered or implied. Use this script at your own risk
- Please do not redistribute this script, please link to this page [Perma-link: http://www.c-amie.co.uk/qlink/?id=142]
- You may not sell or profit from the use of this script
- You may not bundle this script as part of an application deliverable or payload
Download: AddLocalGpStartupScript.zip [4KB]
You can call the script from the Command Line or a bat (batch) file using the following syntax
You can view the help screen and examples at any time by calling
Writes http://www.c-amie.co.uk/ to the file C:\LogFile.log during startup
Opens C:\LogFile.log in Notepad during shutdown
Calls D:\Scripts\MyScript.cmd with no arguments during shutdown
Executes the PowerShell Script C:\MyPsScript.ps1, ignoring the System Execution Policy during startup
Performing a Test
If you want a simple test to find out if it works, try the following which writes a log trace to two text files on the root of C Drive:
Why isn’t there a Logon and Logoff Script Version?
There is actually one and it doesn’t work. The process of installing the Logon Script isn’t quite a simple as the process for a Startup Script because it has to be written into the registry on each user account. Consequently, until such a time that I have the will to automate this part, while it performs the installation legally, it doesn’t execute unless you go in and press the apply button on the Logon Script UI.
- Windows Vista
- Windows 7
- Windows Server 2008, 2008 R2
You know that something a bit odd is going on when one of a batch of servers starts throwing errors that the others sailed past. In this case trying to configure PEAR for a new PHP install with Mail, Mail_Mime and Net_SMTP (pear.php.net/mail, pear.php.net/mail_mime and pear.php.net/net_smtp) should be fairly standard. The other servers took the install and even this server too Mail and Mail_Mime but would not accept Net_SMTP returning:
Leaving it overnight before rolling up my sleeves (in case it was just downtime at the package repository) the fix was fairly simple.
If you are experiencing the same problem this server was having, running the following
Will result in
If you get something akin to the above simply browse to:
and delete the pear folder
- Windows Vista, SP1, SP2
- Windows 7, SP1
A slight matter of a documentation error on TechNet that has existed for a very long time and is causing a lot of confusion.
TechNet states that the first and preferred search location for an Unattend.xml file is the registry location:
This is vague and confusing and is in fact probably typo that has been left for a long time. This could mean a value called Setup!UnattendFile under HKLM\System or a number of other things.
You can see the TechNet link below.
View: Manual Installation of Windows 7: Overview
I can confirm from first hand experience with Vista, 7 and 7 SP1 that this should be:
Unattend.xml files found through this registry key do not have to be named Unattend.xml, you can call them whatever you like.