Windows 7 Backup - System image includes non system disk

Hi,
I am trying out windows 7 backup, hoping at last that I won't need a 3rd party backup solution. So far so bad!
My first problem is how ridicilously slow the backup is, but this has been discussed at length elsewhere. My second problem is the backup stalls when I try to backup a folder which I know has got various bits of malware in. I am an IT pro and use the files in this folder for testing purposes. OK fair enough I guess, although I think the backup should handle this event a bit more elegantly. So I've zipped and password protected the offending files to hide them from the AV (security essentials by the way)
The final problem which I just can't understand is that when I try to create an image of my system drive, backup wants to add my D drive (which is purely a data drive) to the image. My D drive is huge and I don't want to include it in a system image. I keep my system drive lean and mean for exactly this purpose but now I can't back it up because the total size of C and D drives combined exceed the capacity of my backup drive.
I know for a fact that the D drive has no consequence to the system boooting or operating, I have disconnected it and windows boots up just fine. In computer management the D Drive is not showing up as a system drive, so why does windows think it is? And why isn't there a power user mode wher I can choose exactly what I want in a system image, I understand you're trying to make windows easy to use for the average Joe, but this lack of functionality and in depth control feels more like a Mac than windows.... and I hate macs.
So can anyone shed any light as to why my D drive is being flagged as a system disk, otherwise it's back to 3rd party solutions... AGAIN
Thanks

There is a solution.
Microsoft usually have stuff that is not documented. For example Windows server 2008 comes with a command line utility that will allow the backup (in this case a shadow copy) of any drive you wish to a backup target. The program is wbadmin.exe.
According to some Microsoft sources it doesn't exists on Windows 7 but let me assure you that it does; I use it all the time, specifically to get round the problems you have described in your posts.
I build VHD images and test them until I am happy with them and then I back them up as a system image and then rewrite them on to a system drive. I can only do this with wbadmin.exe
To backup your c: to your d: (or what ever other drive you have space on in this case we will use d:)
- Open a command prompt as Administrator
- Run the following command:
Wbadmin start backup -backupTarget:d: -include:c: -quiet
- You should get output something like this:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Retrieving volume information...
This will back up volume System(C:) to D:.
The backup operation to D: is starting.
Creating a shadow copy of the volumes specified for backup...
Creating a backup of volume System(C:), copied (1%).
Creating a backup of volume System(C:), copied (29%).
Creating a backup of volume System(C:), copied (57%).
Creating a backup of volume System(C:), copied (79%).
Creating a backup of volume System(C:), copied (98%).
The backup of volume System(C:) successfully completed.
The backup operation successfully completed.
Summary of the backup operation:
The backup of volume System(C:) successfully completed.
That should complete the backup. It should create a WindowsImageBackup folder in the dirve you backed up to.
Restore as normal.
There is one small but very important caveat: If you have any system files or programs that are linked to the system drive on your d: drive or elsewhere you may find that when you restore your system the links are broken. it should not happen if you
have not made any changes before you restore but if you are like me who use the d: to store the bulk of the program files and just use the c: to store the system OS (on SSD... the need for speed! :) ) then you need to be careful... be warned!!
That's all folks!
Bick

Similar Messages

Windows Backup fails to complete and System shows 29 Restore Points all titled "System Image restore point" but none will work.

Problems both seemed to appear about the same time and may be related.
Had backups on an external drive prior to the problem and appeared to be working. I have since cleaned the external drive in an attempt to start a new backup series but it continues to stop and report backup has failed.
The System restore was working fine and one day it had changed all the existing Restore Points to "System Image restore point"
but still showed all the different dates. In the System Properties window it indicates that there are 0 bytes in "current usages",
which I assume they are all empty but I can't create any new ones. I get Error code 0x80042308.
I have tried the Clean Boot with no results. I use MS Security Essentials for virus protection.
I have no other symptoms or problems on the PC.
About ready for a Recovery and start all over.
George M1

Hi,
Your first step should be to run chkdsk /r /f on all the drives in that computer. Shadow copy errors are often caused by disk problems (usually minor) which chkdsk will find and correct.
Also, this issue can be caused that VSS dlls are corrupted.
Re-install the VSS dlls by following these steps:
a. Using command prompt, CD to the WINDOWS\system32 directory
b. Stop the Volume Shadow Copy service by executing the command "net stop vss"
c. Register the following DLLs and services by executing these commands:
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
Hope these could be helpful.
Kate Li
TechNet Community Support

System Image Restore Fails "No disk that can be used for recovering the system disk can be found"

Greetings
                                    - Our critical server image backup Fails on one
server -
Two 2008 R2 servers. Both do a nightly "Windows Server Backup" of Bare Metal Recovery, System State, C:, System Reserved partition, to another storage hard drive on the same machine as the source. Active Directory is on the C: The much larger D: data
partition on each source hard drive is not included.
Test recovery by disconnecting 500G System drive, booting from 2008R2 Install DVD, recovering to a new 500G SATA hard drive.
Server A good.
Server B fails. It finds the backed-up image, & then we can select the date we want. As soon as the image restore is beginning and the timeline appears, it bombs with "The system image restore failed. No disk that can be used for recovering the system
disk can be found." There is a wordy Details message but none of it seems relevant (we are not using USB etc).
At some point after this, in one (or two?) of the scenarios below, (I forget exactly where) we also got :
"The system image restore failed. (0x80042403)"
The destination drive is Not "Excluded".
Used   diskpart clean   to remove volumes from destination drive. Recovery still errored.
Tried a second restore-to drive, same make/model Seagate ST3500418AS, fails.
Tried the earliest dated B image rather than the most recent, fail.
The Server B backups show as "Success" each night.
Copied image from B to the same storage drive on A where the A backup image is kept, and used the A hardware to attempt restore. Now only the latest backup date is available (as would occur normally if we had originally saved the backup to a network location).
Restore still fails.         It looks like its to do with the image rather than with the hardware.
Tried unticking "automatically check and update disk error info", still fail.
Server A SRP 100MB C: 50.6GB on Seagate ST3500418AS 465.76GB Microsoft driver 6.1.7600.16385   write cache off
Server B SRP 100MB C: 102GB on Seagate ST3500418AS 465.76GB Microsoft driver 6.1.7600.16385   write cache off
Restore-to hard drive is also Seagate ST3500418AS.
http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/e855ee43-186d-4200-a032-23d214d3d524      Some people report success after diskpart clean, but not us.
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/31595afd-396f-4084-b5fc-f80b6f40dbeb
"If your destination disk has a lower capacity than the source disk, you need to go into the disk manager and shrink each partition on the source disk before restoring." Doesnt apply here.
http://benchmarkreviews.com/index.php?option=com_content&task=view&id=439&Itemid=38&limit=1&limitstart=4
for 0x80042403 says "The solution is really quite simple: the destination drive is of a lower capacity than the image's source drive." I cant see that here.
Thank you so much.

Hello,
1. While recovering the OS to the new Hard disk, please don't keep the original boot disk attached to the System. There is a Disk signature for each hard disk. The signature will collide if the original boot disk signature is assigned to the new disk.
You may attach the older disk after recovering the OS. If you want to recover data to the older disk then they should be attached as they were during backup.
2. Make sure that the new boot disk is attached as the First Boot disk in hardware (IDE/SATA port 0/master) and is the first disk in boot order priority.
3. In Windows Recovery Env (WinRE) check the Boot disk using: Cmd prompt -> Diskpart.exe -> Select Disk = System. This will show the disk where OS restore will be attempted. If the disk is different than the intended 2 TB disk then swap the disks in
correct order in the hardware.
4. Please make sure that the OS is always recovered to the System disk. (Due to an issue: BMR might recover the OS to some other disk if System disk is small in size. Here the OS won't boot. If you belive this is the case, then you should attach the
bigger sized disk as System disk and/or exclude other disks from recovery). Disk exclusion is provided in System Image Restore/Complete PC Restore UI/cmdline.
5. Make sure that Number and Size of disks during restore match the backup config. Apart from boot volumes, some other volumes are also considered critical if there are services/roles installed on them. These disks will be marked critical for recovery and
should be present with minimum size requirement.
6. Some other requirements are discussed in following newsgroup threads:
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/871a0216-fbaf-4a0c-83aa-1e02ae90dbe4
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9a082b90-bd7c-46f8-9eb3-9581f9d5efdd
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/11d8c552-a841-49ac-ab2e-445e6f95e704
Regards,
Vikas Ranjan [MSFT]
------- This information is provided as-is without any warranties, implicit or explicit.-------

Time machine backups no longer include hidden system folder like /usr and /sbin

My Time Machine backups Aug - Oct seem complete. When I look at them I see all the expected folders and files. Starting in November key system folders disappeared: /sbin, /usr, /bin, etc. However, the non-hidden one are there: /Applications, /Library, etc. Later in November certain things show up again like /usr/share/man/whatis and /usr/share/man/ri, but nothing else under /usr/share. I've looked for all possible places where folders might be excluded and have found nothing.
I'm using Mavericks on a MacBook Pro with a Time Capsule. All software and firmware are completely up to date. I can't explain the behavior. If I take one example I can see /usr in the Nov 5 backup and it is fully populated. It is gone in the Nov 12 backup. In the Nov 19 backup it is back but only with /usr/share/man/whatis. There are no errors in my logs although my logs don't go back that far, so if something happened the week of Nov 5 I don't know.
Anyone with any guesses?
K-Family

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Installing additional Windows 8 on the second, non system, hard drive

GE60 2QE Apache Pro (128GB SSD System + 1TB 7200rpm Data)
1 May i create a bootable primary partition on the 1TB hard disk
and install additional Windows 8.1 on it ?
2 Will it affect MSI's System Recovery in any way ?
3 Would it affect the original windows 8.1 installed on the SSD ?
4 Should i set/tweak anything in the BIOS for the installation ?
5 Am i asking the right and/or the whole questions ?
6 Am i missing something ?
Thanks

The following answers are based on my past experience, but I personally didn't set up dual systems before. So they're just for your reference.
1. Yes.
2. No. The MSI's system recovery image is in the hidden partition. Unless you delete that partition, installing new OS won't touch it.
3. Yes, because you are about to install dual copies of Win 8.1.
4. No need to set anything in BIOS.
5. Can't answer.
6. Won't know until you actually start this project.

MOVED: Installing additional Windows 8 on the second, non system, hard drive

This topic has been moved to GAMING Notebooks, since the topic does not belongs to Windows 8 upgrade board.
https://forum-en.msi.com/index.php?topic=255537.0

The following answers are based on my past experience, but I personally didn't set up dual systems before. So they're just for your reference.
1. Yes.
2. No. The MSI's system recovery image is in the hidden partition. Unless you delete that partition, installing new OS won't touch it.
3. Yes, because you are about to install dual copies of Win 8.1.
4. No need to set anything in BIOS.
5. Can't answer.
6. Won't know until you actually start this project.

Using Bootcamp system image on Non-Mac PC

Hi Guys,
I'm in the process on moving my bootcamp system to a separate computer but it's not a mac system. I am wondering if there are things I should watch out for. Like what happens to apple related applications like icloud panel, bootcamp panel, itunes, apple drivers etc. Will those corrupt my windows?

Just back up your documents/important data and install Windows from scratch on your new machine. Doing a migration any other way opens you up to far more headaches.

Cannot burn system image to Blu ray disks via LGwh16ns40

First thing it will not write to disk, unless i format the disk. Once formatted the Image program writes to the disk. But issue is when it finishes the first disk (it told me to label it disk 1), it ask for another disk, but writes the same info and asks
to label it again (disk 1). I have an LG WH16NS40 manufatured June 2014. can someone tell me if im doing something wrong?!!

Hi acura1073,
We indeed need more information about your problem so that we can help.
What’s about the “Image program”?
If you have any screenshots, this would be better to understand your situation.
Alex Zhao
TechNet Community Support

Operating System Image VS Operating System Installer - what does everyone recommend and which is quicker?

I have worked out that all of the configuration in our windows 7 image can be applied through the task sequence after the operating system is installed. Currently we apply and image and then add configuration.
I am wondering would I be better off just adding a Windows 7 installer instead of imaging? Which method would be quicker?
Would be interested to see how everyone does this.
One thing to consider is windows updates, as if we have an image (WIM file) we can inject updates to it through software update point on patch Tuesday to save having to apply them through the task sequence. We can't inject updates into the installer so time
taken to install 100 odd patches has to be taken into consideration.

The only reason to use an Installer post SP1 is for legacy OSes like XP or Server 2003 where no image actually exists on the media. Pre-SP1, there were issues with drive letters because of an on-going, back-and-forth mis-match of assumptions between the
Windows team and the ConfigMgr that required you to build an image from the actual installer. This was resolved in SP1 through the use of the OSDPreserveDriveLetter task sequence variable. There's a also a supportability issue when using an OS Installer --
I don't remember the details off hand though I know I wrote about them in the unleashed book if you are curious.
Thus, unless you are deploying XP or 2003, you should be using images only -- either image.wim directly (which you really should only use in a build and capture) or yur recaptured image.
Jason | http://blog.configmgrftw.com | @jasonsandys

How to Delete Non-System State Backups in Windows 2008R2

Hello,
I am running a Windows 2008R2 server which uses Windows Server Backup to do the backups. We are using the backup-tool to create non-system state backups of the data-directories on this machine. The backup is done on a dedicated disk connected through iscsi
(to a Synology box). This backup disk has become too small and we have now replaced the Synology box with a bigger one. Here i created a new LUN again for the backup purposes.
Now for my question; The wbadmin.exe tool supplied with W2008R2 does not offer a way to delete the old backups. I know that in Win2012 (which we we also have running) I could add the new iscsi location and then (when enough backups are available on the new
target) use wbadmin.exe delete backup to delete the old non-system state backups; e.g.
wbadmin delete backup -version:08/07/2013-21:00
This (very undocumented) feature of Windows 2012 and higher works quite nice and is exactly what i am searching for on the W2008R2 machine; a way to delete the old backups (and under the hood delete the corresponding snapshots)
I've done quite a bit of research and it should be possible to do something similar in 2008 but then manually, The howto is described in the following link: http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx .
Basically it describes that you should use DiskShadow.exe to remove e.g. the oldest snapshot with a command like :
Delete shadows OLDEST \\?\Volume{7fc1871b-2e1f-11dd-a339-001e4fb7af35}
Windows Server backup (wbadmin) should then on the next run 'see' this deletion and update its list of available backups:
"You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during
the next backup."
I've done this on our box and it indeed removes the shadows from the list. However, in the Windows Backup 'dashboard' it still lists the backups as available. Also after a new backup has finished (according the the article this is when it should 'update'
its backup catalog). When I try to restore a backup from a date that i just removed it gives a nice message that this is impossible because the snapshot is not available (duh :)) ;
Unable to browse Local disk. The shadow copy of the backup stored on the backup destination cannot be found.
So it seems that the aforementioned method works; it removes the snapshot and frees diskspace, but it doesn't update the Windows Backup catalog. As a result the management tool (GUI) still lists the backups which are no longer available! How can i change
this? Is there any way to do this? I found one article which mentions that the Dashboard bases its screen on the Windows Logs and not on the actual VSS snapshots available:
http://forum.wegotserved.com/index.php/topic/23757-start-afresh-with-server-backup/ (WHS) In my situation however this seems unlikely because i don't have any logs that date back as far as my backups go.
In my opinion this is a real bug and it leaves us with a in-consequent backup schema. Does anyone have similar situations or even a solution to my problem?
Kind Regard, Martin

Hi Mandy,
Yes! I think i got my answer and I now get how windows backup works in Windows 2008 :-) It turns out that I dismissed some suggestions a bit too soon. The answer lies in the command mentioned earlier :
Wbadmin delete catalog
This command does delete all the backups from a perspective of the Windows Backup UI, but leaves the VSS snapshots intact. This means that the backups are still available, but you just can't restore them with the User Interface. In order to 'update' the
UI with the current available snapshots (which you can list with diskshadows list shadows all), you have to re-add the existing media on which the backups took place using the Wizard of the UI. It will then inform you that existing backups are available and
if you want to keep these for restore purposes. If you click 'yes', and THEN perform a backup ... All the current available backups will be shown in the User Interface :-)
So for my steps taken to change from one iscsi (iscsi1) to another (iscsi2):
- Add the 2nd iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Add more backup destinations -> iscsi2
- Remove the 1st iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Remove current backup destinations -> iscsi1
- Run some backups on the new destination. Old restore points are now still available. When enough restore points are available on the new volume iscsi2 start deleting old data from iscsi1 as follows:
- Run diskshadow
diskshadow
- list all the current snapshots
list shadows all
- remove all the snapshots of iscsi1 (repeat until all shadows are gone of iscsi1)
delete shadows oldest \\?\volume{yourvolumeid}\
- delete the windows backup catalog
wbadmin delete catalog
- Restart the windows backup UI and re-add your schedule on the new volume iscsi2. It will now ask if you want the keep the existing data for restore purposes; click yes.
- After the next backup only the backups of volume iscsi2 will be listed and everything is fine !
I Hope my post will help others with similar questions. It was quite a search before I understood the way it works. Basically as long as your VSS snapshots are still available and listed by diskshadow you still have the backups and you will be able to get
this in sync with the steps above (delete schedule and re-add originating targets containing the snapshots). After the next backup the UI will update itself.
(In my case someway along the way I lost my originating snapshots, but because I already had my new backup set it didn't bother me; It kept me from having to delete all 510 old backups :) with diskshadow)
Regard, Martin

Window System Image Backup Fails to Back Up EFS System Partition

I am trying to use WBADMIN to take a complete system image of my system with the following command:
wbadmin start backup -backuptarget:[NETWORK SHARE] -include:C: -allcritical
WBADMIN is able to create shadow copies of all the volumes on my system, but when it begins to create a backup of the EFI System Volume, it fails immediately:
The backup operation to [NETWORK SHARE] is starting.
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a backup of volume SYSTEM(EFI System Partition) (300.00 MB), copied (0%).
Summary of the backup operation:
The backup operation stopped before completing.
The backup operation stopped before completing.
Detailed error: The I/O operation has been aborted because of either a thread exit or an application request.
Log of files successfully backed up:
C:\WINDOWS\Logs\WindowsBackup\Backup-01-02-2014_18-45-09.log
Log of files for which backup failed:
C:\WINDOWS\Logs\WindowsBackup\Backup_Error-01-02-2014_18-45-09.log
There was a failure in preparing the backup image of one of the volumes in the backup set.
The I/O operation has been aborted because of either a thread exit or an application request.
The system is encrypted with Bitlocker, and does not have a TPM. I am also running Carbonite, but I have disabled it and the results are the same.
No data is actually written to the log files either, which is strange. The GUI System Image Backup utility also provides virtually the same error. Any thoughts?

Hi,
Try to test in WinRE to see what the result is.
Alex Zhao
TechNet Community Support

Can 5 axis image stabilization be engaged with non system lenses for A7II and A7rII?

Many people use/will use their excellent non system manual focus non system macro lenses on the A7II and undoubtedly on the soon to be released A7RII. Stabilization in the X/Y planes is very very important for macro. Sony on the A7II only stablizes the X/Y planes for lenses that report the focus distance as best I can tell. Perhaps the lens compensation app or another can be modified so this data can be manually inputted or even change the firmware to allow this and thus stabilize all 5 axes. Focal length will need to be inputted of course as well. Perhaps there is another way around this that I have missed. Thanks for any comments.

Thank you for taking the time to answer. I have done more digging in reviews and recalled sony's announcments which implied on 3 axis IS is available w/o a lens that reports focsing distance. Not my favorite source, but review from PCMag: "If you're using a non-native lens, or even a native manual focus lens like the Zeiss Loxia 2/50, it's stabilized along three axes—yaw, pitch, and roll. There's a technical reason for that. In order to compensate along the x and y axes, the camera needs to know the distance to the subject, which requires electronic communication of the focal distance from the lens to the body. To compensate for the other three axes, the only data that needs to be transmitted is the focal length of the lens. Even if you're using a purely mechanical Leica lensit can be stabilized—you're able to manually enter the focal length via a menu. The only real downside to this is that the A7 II does not add that focal length to the recorded EXIF data, so if you like to track which lens a shot is captured with, you'll need to take notes." http://www.pcmag.com/article2/0,2817,2475439,00.asp A friend informed me that on his A7II he must mount a non OSS Sony lens first to have any image stabilization with any of his totally manual lenses--seems the camera saves the settings of the last lens attached. Turning the cam off doesn't reset this--very odd---seems to be a bug in the firmware. I hope the A7rII is different. This whole issue is quite confusing. Appreciate any additonal clarification.

Allow 5 axis image stabilization for non system lenses in A7(r)II series

Many people use/will use their excellent non system manual focus non system macro lenses on the A7II and undoubtedly on the soon to be released A7RII. Stabilization in the X/Y planes is very very important for macro. Sony on the A7II only stablizes the X/Y planes for lenses that report the focus distance. Perhaps the lens compensation app can be modified so this data can be manually inputted or even change the firmware to allow this and thus stabilize all 5 axes. Focal length will need to be inputted of course as well. If the new field is left blank, no action is taken as not to affect users not interested in this feature. Olympus somehow allows all 5 axes to be stabilized just by putting in the focal length but it is not clear how they pull that off. Thank you for considering this.

Thank you for taking the time to answer. I have done more digging in reviews and recalled sony's announcments which implied on 3 axis IS is available w/o a lens that reports focsing distance. Not my favorite source, but review from PCMag: "If you're using a non-native lens, or even a native manual focus lens like the Zeiss Loxia 2/50, it's stabilized along three axes—yaw, pitch, and roll. There's a technical reason for that. In order to compensate along the x and y axes, the camera needs to know the distance to the subject, which requires electronic communication of the focal distance from the lens to the body. To compensate for the other three axes, the only data that needs to be transmitted is the focal length of the lens. Even if you're using a purely mechanical Leica lensit can be stabilized—you're able to manually enter the focal length via a menu. The only real downside to this is that the A7 II does not add that focal length to the recorded EXIF data, so if you like to track which lens a shot is captured with, you'll need to take notes." http://www.pcmag.com/article2/0,2817,2475439,00.asp A friend informed me that on his A7II he must mount a non OSS Sony lens first to have any image stabilization with any of his totally manual lenses--seems the camera saves the settings of the last lens attached. Turning the cam off doesn't reset this--very odd---seems to be a bug in the firmware. I hope the A7rII is different. This whole issue is quite confusing. Appreciate any additonal clarification.

Window can not find a system image on this computer

I have HPPavilion dv6 3134se notebook.when I purchased.its operating system was windows 7 home basic.My friend suggest me to upgrade windows 7 ultimate.he also give dvd of windows 7.i have installed it.after3days a message appear from microsoft.that your copy is not original.ITry to get my previous windows 7 home basic.when i press F 11&force to recovery amessage apear tahat window can not find a system image on this computer.I try to my level find it a message appear.thatspecify the location of the system image.How search system image on the network pleasehelp me with url address&my hp recovery partion also now not loki ngcomputer.i hope some one help me.
This question was solved.
View Solution.

Hi,
You're welcome, glad it helped
All the best,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

System image/snapshot for restoring entire system.

1- I want to make "system images"/"snapshots" of my computer for a later restore.
2- Also i would like to learn more about how to restore "system images" of my system.
note: since time machine works incremental i dont want that because i cannot isolate a system image.
thank you,
Paulo

PauloGuedes wrote:
1- I want to make "system images"/"snapshots" of my computer for a later restore.
2- Also i would like to learn more about how to restore "system images" of my system.
note: since time machine works incremental i dont want that because i cannot isolate a system image.
Time machine does do just that. you just misunderstand how it works. you can do a full system restore from Time machine to any time point you have a backup for and it will give you an exact copy of your system (minus some temp files) at that time. to do a full system restore from TM you boot from the leopard install DVD and select "restore system from backup" from the utilities menu.
thank you,
Paulo
Message was edited by: V.K.

Windows 7 Backup - System image includes non system disk

Similar Messages

Maybe you are looking for