SYSPREP problem

Similar Questions

• Tecra M5 Sysprep problem with file hdaudbus.sys

  We have a syspreped image, that was created on a Toshiba Tecra M2.

  Our current image works on the following model of machines: -.

  Toshiba Portege 4000
  Toshiba Portge 4010
  Toshiba Portege M100
  Toshiba Portege R100

  Toshiba Tecra M2
  Toshiba Tecra S1

  Toshiba Satellite Pro 6000
  Toshiba Satellite Pro 6100
  ----------------------------------------------------------------------------------

  We should now get the image while you work with the new Toshiba Tecra M5.

  The driver that I have a problem with is HDAUDBUS.sys

  When the machine starts first, and almost before it even tries to build some itsself, it says it cannot find the file 'hdaudbus.sys' and it seems that it is in the D: research, if you navigate to system32\drivers, then the driver is installed correctly, but I can't seem to automate this process.

  I copied all required driver files and inf.
  I filled the sysprep.inf (under the heading "OemPNPDriversPath") file with the driver and the correct path. It made no difference. I also 'DriversSigningPolicy' value 'IGNORE '.
  I have sysprep using the image - pnp, mini installation then close it carefully.

  The question is:-

  (A) I do something wrong, and is there a good way to get windows/sysprep automatically install this driver?

  (B) I have a fix for the problem above, is:--
  Put our sysprep would be the image on the Tecra M5, manually installed ALL of the correct drivers and then re-Sysprep image. The question is, is it OK to do this? (It seems to work)? Or is it not advisable to sysprep image, several times, on different model machines?

  Any advice would be appreciated!

  Thank you

  Hello Mark

  Your ad is very interesting, but I don't really know which should help you. As you can see that he is user in the forum and you'll be lucky if anyone can tell you anything about your problem.

  This file is Microsoft one and try to check in a Microsoft support page, if there is solution available.

  In any case good luck!

• Strange view Domain Join Sysprep problem 5.3.1.

  I have a strange problem and I am pulling my hair out.  I have a win7 machine pool is not join the domain at all when dial or redial.  I use sysprep with a specification of customization that I have used for previous pools without problems.  I did a regular clone and use the specification of customization and everything went well.  I can fight my way through and get them joining the field via vcenter, but is not viable in the long term.  Out of curiosity, I logged into two so that they were waiting to start their sysprep (just after they have been cloned) and grabbed the sysprep.xml file.  They are identical, but with a major and an important difference in the identification of the sysprep.xml file section. The view composer, just looks like he wants to join the Working Group, while the clone of vcenter shows he wants to join the domain.  (Details below)  Is there that a difference in the way composer manages customization as vCenter?

  It sounds like what I expected (via the regular vcenter clone, details deleted):

  < identification >

  Domaine.org < JoinDomain > < / JoinDomain >

  < References >

  < username > [email protected] < / username >

  < EncryptedPassword > 8... 892 < / EncryptedPassword >

  Domaine.org < domain > < / domain >

  < / qualifications >

  < / identification >

  That's what one on linked clone desktops has, it looks like something a little 'good thars yer problem ":

  < identification >

  < JoinWorkgroup > WORKGROUP < / JoinWorkgroup >

  < / identification >

  Any help/info is appreciated.

  It was very weird, I had to support.  After several hours to prove what was going on, I transferred to the next call center who knew a guy who happened to remember a case strange and found an obscure article!  Here is the fix:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2080397

• An error occurred when querying for the pending operations

  Original title: sysprep problem
  I have an acer aspire 5738Z, I use windows 7 (64 bit) I try to open sysprep.exe and it does not open, a text box appears saying "an error occurred when querying for the pending operations. What can I do to fix this?

  Hello

  Thanks for posting the request in the Microsoft community forums.
  I understand that you receive the error "an error has occurred when querying for outstanding operations" when trying to open sysprep.exe on the computer.

  You can try the solutions provide and check if it helps solve the issue.

  Method 1:
  You can scan System File Checker to fix corrupted files.
  How to use the System File Checker tool to fix the system files missing or corrupted on Windows Vista or Windows 7
  http://support.Microsoft.com/kb/929833

  Method 2:
  If the steps above fail then you can try the steps and check.

  a. run regedit by typing regedit in start search by pressing ENTER.
  b navigate to the following key:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  Key: RegistrySizeLimit
  Type: REG_DWORD
  Value: 0xffffff (4294967295)
  c. reset.

  If you need help with Windows, keep us informed. We will be happy to help you.

• 10 SYSPREP Windows problems

  Hello! This is my first post on this forum. I started to use DIA this year as Dell advised us that future machines must be photographed using the DIA. I have successfully created an image of Windows 7 in January, and my colleague built a picture of "laboratory" as well and downloaded to Dell.

  I built also with success a 'Version 1' or Beta build of Windows 10 education. However, we decided that we have to activate several default privacy options, and I also wanted to change a few things, so I started trying to build a Version 2. However, I have not managed to bring this to pass the phase of Sysprep.

  I started relying on the same machine I used for Version 1, a Latitude E6320. I thought I could just start on the 1 Version and make my changes and re-sysprep it. But I got errors like below. So (TWICE), I have rebuilt the image from scratch, this time using a Parallels virtual machine.

  But this is the error I got when using the capture tool DIA with verified Sysprep:

  Sysprep.exe/Export Failed "C:\Dell_PE_Folder\bcd_store_save".

  Error code: 0

  Please contact Microsoft for this error. Otherwise, please restore an earlier version of this image and then try to run through the tools.

  C:\Windows\System32\Sysprep\Panther\setuperr.log exists.

  Please read this file for more details. C:\Windows\System32\Sysprep\Panther\setuperr.log "C:\Windows\Panther\DTRI\LOGS\Auto_Capture_Prep_Tool.log".

  The files listed in the above log file may need to be deleted if they exist, or who are removed from the registry:

  HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownfiles

  At this point, this system is unusable. The start menu button does not work, and most of the commands run get the error "the device is not ready".

  However, here's what's in the newspapers:

  Setuperr.log

  SYSPRP error 0 x-2147216616: failure to reactivate the custom trigger Compat-maxime.

  SYSPRP setupdigetclassdevs failed with error 0

  I tried to look for errors, but did not come with anything useful on Google.

  I checked Auto_Capture_Prep_Tool.log, is very long, but it ends with the same text as I already entered above.

  I am unable to run regedit (the device is not ready error) and put in network is disabled, so I can't do the remote registry it is.

  One remark to make, it's that I'm currently building the picture with too few applications preinstalled Windows store as possible. I used a few Powershell commands to remove unwanted applications. It's the resource that I used for this:

  

  Specifically, the first post with a powershell script.

  I also used Spybot anti-phare to privatize as much as possible.

  

  Does anyone have recommendations?

  I came across some problems this week with updated appx packages after execution of Windows on 1511 (TH2) updates.  Create a batch with the following content file and run before sysprepping.  Worked for me.

  Echo Off
  CLS
  Echo removing some packages Appx interfering with Sysprep
  PowerShell - executionpolicy remotesigned Remove-AppxPackage - Microsoft.Appconnector_1.3.3.0_neutral__8wekyb3d8bbwe Package
  PowerShell - executionpolicy remotesigned Remove-AppxPackage - Microsoft.People_10.0.2840.0_x64__8wekyb3d8bbwe Package
  PowerShell - executionpolicy remotesigned Remove-AppxPackage - Microsoft.Getstarted_2.3.7.0_x64__8wekyb3d8bbwe Package
  PowerShell - executionpolicy remotesigned Remove-AppxPackage - Microsoft.Office.OneNote_17.6131.10051.0_x64__8wekyb3d8bbwe Package
  PowerShell - executionpolicy remotesigned Remove-AppxPackage-package microsoft.windowscommunicationsapps_17.6308.42271.0_x64__8wekyb3d8bbwe
  PowerShell - executionpolicy remotesigned Remove-AppxPackage - Microsoft.MicrosoftSolitaireCollection_3.3.9211.0_x64__8wekyb3d8bbwe Package
  PowerShell - executionpolicy remotesigned Remove-AppxPackage - Microsoft.SkypeApp_3.2.1.0_x86__kzf8qxf38zg5c Package
  : All the

• Problems between virtual el Centre "Sysprep" y el servidor VDM

  Hola todos,

  Tengo el siguiente stage

  Tengo a Virtual Center server y tengo 4 ESX 3.5 todo conectado por fibra switches y UN servidor VDM todo running usually, pero despues una Migración than did Virtual Center 2.5 del toward a nuevo servidor, the creation of Poole automaticos desde el VDM no don't works adecuadamente for example no antes of the yo creaba Migración a pool of 5 maquinas y el servidor VDM creaba las maquinas el mismo El cambiaba el cinco number y las blog al dominio if fuera el caso.

  ahora, despues of the Género Migración a pool of 5 United Nations maquinas model y todas las cinco maquinas however generated only con todas despues el mismo number than original model el

  any of ustedes ha tenido este problema o saben como delivery problems of este

  MUCHAS gracias por su ayuda

  Hola, quisiera help you también con este problema.  Tal vez the first Québec prueba you recommend hacer're desde vCenter using VI Client tratar crear una nueva Máquina virtual manualmente el using el model xp, esta forma podras verificar as los archivos sysprep estan estan in el correcto directory.

  Saludos,

  Andres Martinez

  Founder and president of virtualizing Technologies LLC

  Blog: http://www.virtualizemos.com

  Twitter: http://www.twitter.com/andresmartinez _

  LinkedIn: http://www.linkedin.com/in/andresmartinez73

• Creation of sysprep for Tecra A9 problem

  I am trying to create a sysprep to Tecra A9 without success.

  The section SysprepMassStorage looking like that.

  [SysprepMassStorage]
  ; Toshiba RAID
  ; S3
  PCI\VEN_8086 & dev_2653 & subsys_0f001179 = 'C:\Drivers\ mass\ToshRaid\KR10I.inf '.
  ; S4
  PCI\VEN_8086 & DEV_27C5 & SUBSYS_0F001179 = 'C:\Drivers\ mass\ToshRaid\KR10I.inf '.
  ; A9
  PCI\VEN_8086&DEV_2829="C:\Drivers\mass\A9\iaahci.i nf."
  ; PCI\VEN_8086 & DEV_2829 = "C:\Drivers\mass\A9\ich8id2.inf".
  ; PCI\VEN_8086 & DEV_2829 = "C:\Drivers\mass\A9\ich8ide.inf".

  PCI\VEN_8086 & DEV_2850 = 'C:\Drivers\mass\A9\ich8ide. INF '.
  ; PCI\VEN_8086 & DEV_2850 = "C:\Drivers\mass\A9\ich8id2.inf".

  I'm good or bad. I have line 2 with the Guid 2829 rem and 1 line with the Guid of 2850.
  Any help would be grateful.

  I put t know exactly what is the fault, but as far as I know, you will need to install the Intel Matrix Storage Manager before you continue the installation of Windows operating system.
  I guess you must include this iMSM in the picture!

  All that s what I can suggest. Maybe this info can be useful for you.

• Cloning of Toshiba laptops with sysprep

  Hello

  We have a lot of different brands and models of laptops and have a sysprep image that we use for all of them and so far had no other problem that have to update the drivers after the laptop has been photographed.

  That is until we started to buy Toshiba laptops!

  After that we photographed the laptop it blue screens with either

  PAGE_FAULT_IN_NONPAGED_AREA

  Stop: 0 x 00000050 (0xF0000223, 0 x 0, 00000002 00000000, 0x806BAF76)

  or a

  STOP 0x0000007B

  Even after the repair of the image it blue screens.

  So far, we had to build a new image for each laptop model Toshiba and then image.

  Any ideas on how I can get my sysprep image to work?

  Hi crystalreef,

  Hmm different laptops have different hardware, so I don't think you can use a single image for all mobile phones. Each computer or laptop model requires the image clean s with own drivers and isn't compatible with other models.

  You can install Windows Toshiba Recovery disk?

• Re: Portege 3440CT - starting problems

  I received a Portege 3440CT by a former colleague. It works under Windows 2000. She has not used in more than 5 years and can't remember what the password was. I tried to log in as administrator with a blank password, but the password has not been left white (grr) so basically I can't cross the password prompt.

  Shouldn't be a problem - there are a lot of Internet password recovery tools. I did a disk using this one here: http://home.eunet.no/pnordahl/ntpasswd/ intending to boot from the disk - there is a brand USB Toshiba external floppy drive.

  HOWEVER: the Portege stubbornly refuses to do. The boot order is set to try the FDD before all other options; I manually told to boot from diskettes; There is no ignoring me and Win2K boot from the hard drive. Would be very grateful for any ideas!

  I do not have:
  a reader of CD or DVD for laptop;
  a network connection or internet on it, as far as I know;
  disk recovery or installation of Windows;
  anyway to start Windows without knowing the password.

  I have:
  USB flash drives / external hard disk drives;
  The installer of Ubuntu (although on a CD, so useless without a CD player?);
  other computers.

  Wipe the hard drive is a solution I'd be happy to see if anyone can advise me on how to do it - there is nothing important about the laptop that should be retrieved.

  Hi abi278,
  first of all: what do you think?

  -install a new os on this machine?
  -use the operating system installed?

  get rid of the operating system administrator password:
  -install the drive in another system and run norhdahls supertool > read each line which is given! It is able to check the registry to another hard drive as the boot device.
  -make an installation of xp on another machine, sysprep this installation and change drive hard back
  -install the drive in another system and make it bootable with back, copy the source files for the system of desires and run the installation after you reinstall hard drive to your ct 3440

  Maybe you need a special player to install...

  BTW: nordahls disc resets passwords * inside * your operating system - read the manual of this powerful tool.

• 400 proOne G2: BSOD when I sysprep ProOne 400 G2 with Windows 10

  Hello

  I have a question I've been working on these past few weeks with no result. I have two HP ProOne 400 G2 that makes Blue Screen of Death, whenever I have run Sysprep on them. I got installed and sysprep with Windows 8.1, but with Windows 10 computers it crashing whenever I try.

  PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PCIEXPRESS

  I assume this has something to do with a bad driver for a device connected to the BUS PCIExpress, but don't know what to do from here.

  I get the following in my analysis of the BSOD:

  Windows Kernel Version 10586 MP (2 processors) 10 free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 10586.0.amd64fre.th2_release.151029 - 1700
  Computer name:
  Core = 0xfffff801 '02e7f000 PsLoadedModuleList = 0xfffff801' 0315dcb0
  The debugging session: Wed Jan 14 11:35:23.343 2016 (UTC + 01:00)
  System Uptime: 0 days 0:27:03.005

  Ebugging details:
  ------------------

  DUMP_CLASS: 1

  DUMP_QUALIFIER: 400

  BUILD_VERSION_STRING: 10586.0.amd64fre.th2_release.151029 - 1700

  SYSTEM_MANUFACTURER: HP

  SYSTEM_PRODUCT_NAME: HP ProOne G2 400 20 inch Touch AiO

  SYSTEM_SKU: L3N70AV

  BIOS_VENDOR: HP

  BIOS_VERSION: N13 worm. 02.02

  BIOS_DATE: 12/11/2015

  BASEBOARD_MANUFACTURER: HP

  BASEBOARD_PRODUCT: 8063

  BASEBOARD_VERSION: KBC Version 05.26

  DUMP_TYPE: 2

  BUGCHECK_P1: 4

  BUGCHECK_P2: ffffe00025cbc038

  BUGCHECK_P3: 0

  BUGCHECK_P4: 0

  BUGCHECK_STR: 0x124_GenuineIntel

  CPU_COUNT: 2

  CPU_MHZ: b58

  CPU_VENDOR: GenuineIntel

  CPU_FAMILY: 6

  CPU_MODEL: 5th

  CPU_STEPPING: 3

  CPU_MICROCODE: 6, 5, 3, 0 (F, M, S, R) GIS: 49'00000000 (cache) 49'00000000 (init)

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

  Nom_processus: svchost.exe

  CURRENT_IRQL: 5

  ANALYSIS_SESSION_HOST: TNI - PC2

  ANALYSIS_SESSION_TIME: 28/01/2016 09:26:11.0835

  ANALYSIS_VERSION: 10.0.10586.567 amd64fre

  STACK_TEXT:
  ffffd001 'a3529e08 fffff801' 02e41f1f: 00000000'00000124 00000000'00000004 ffffe000'25cbc038 00000000' 00000000: nt! KeBugCheckEx
  ffffd001 'a3529e10 fffff801' 0308fe88: ffffe000 ' 25cbc038 ffffe000 '25d0ca98 ffffe000' 25d0ca98 ffffe000 ' 25d275c0: hal! HalBugCheckSystem + 0xcf
  ffffd001 'a3529e50 fffff800' acb08838: ffffe000 00000000'00000750 00000000'00000000 ' 25d0ca04 ffffe000'27994010: nt! WheaReportHwError + 0 x 258
  ffffd001 'a3529eb0 fffff800' acb015c2: ffffd001 ' 9eff6c80 ffffd001 'a3529f50 ffffd001' a34f1180 ffffe000 ' 24add200: pci! ExpressRootPortAerInterruptRoutine + 0x24c
  ffffd001 'a3529f10 fffff801' 02e83387: ffffd001 '9eff6c80 00000000' ffff6dd1 00000000' 158aa449 00000000'00000010: pci! ExpressRootPortInterruptRoutine + 0 x 22
  ffffd001'a3529f70 fffff801'02 fc 2168: ffffd001 '9eff6c80 ffffe000' 27a 49040 00000000' 000001ba ffffe000'27414440: nt! KiCallInterruptServiceRoutine + 0 x 87
  ffffd001 'a3529fb0 fffff801' 02fc23f7: 00000000'00000000 00000000'00000001 fffff801 00000000' 0000002f'0319 c 180: nt! KiInterruptSubDispatch + 0 x 108
  ffffd001 'a9ca5490 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiInterruptDispatch + 0 x 37

  STACK_COMMAND: kb

  THREAD_SHA1_HASH_MOD_FUNC: 0e50fe8fa1ecf43925e43bd200d7bb6400cb19fc

  THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b3258f674ee33805ab3940241ac9889fab704dc3

  THREAD_SHA1_HASH_MOD: 7ec0dd05e870653df55cacfdf5a6b10cad863ce2

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: GenuineIntel

  Nom_image: GenuineIntel

  DEBUG_FLR_IMAGE_TIMESTAMP: 0

  IMAGE_VERSION:

  FAILURE_BUCKET_ID: 0x124_GenuineIntel_PCIEXPRESS

  BUCKET_ID: 0x124_GenuineIntel_PCIEXPRESS

  PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PCIEXPRESS

  TARGET_TIME: 2016-01 - 14 T 10: 35:23.000Z

  OSBUILD: 10586

  OSSERVICEPACK: 0

  SERVICEPACK_NUMBER: 0

  OS_REVISION: 0

  SUITE_MASK: 272

  PRODUCT_TYPE: 1

  OSPLATFORM_TYPE: x 64

  OSNAME: Windows 10

  OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

  OS_LOCALE:

  USER_LCID: 0

  OSBUILD_TIMESTAMP: 2015-10-30 03:15:45

  BUILDDATESTAMP_STR: 151029-1700

  BUILDLAB_STR: th2_release

  BUILDOSVER_STR: 10.0.10586.0.amd64fre.th2_release.151029 - 1700

  ANALYSIS_SESSION_ELAPSED_TIME: 6261

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:0x124_genuineintel_pciexpress

  FAILURE_ID_HASH: {0aebd40d-d4c8-456d-b299-4fede7e8bf0c}

  Best regards

  Thomas

  Best regards
  
  Thomas
  http://www.techwork.dk

  Hello

  HP has a solution for me and are working on a new BIOS to correct the problem of permanence.

  Go to the configuration of the BIOS F10-> advanced-> System Options-> and uncheck 'allow PCIe/PCI SERR # Interrupt.

  Then, you are able to run Sysprep without blue screen of death.

  I see that HP has released a new BIOS version 02.03 last month. You might want to try everything first, but if not, try the above solution.

  Best regards

  Thomas

• Tecra M9: BSOD after starting syspreped image

  Hello

  a windows xp pro, I built the image on a tecra 9100 and managed to get almost all of our cell phones started syspreped image here is the Tecra M1, M2, M3, M5 and Portege R100, R200 and a R500.

  However, I get a blue screen of death when I try to start the M9. I found a few posts that say when the image was created to UNINSTALL the host IDE controllers and then run the command sysprep.

  It helped when we had problems with the portege R500 however the M9 turns out to be embarrassing.
  Someone at - it ideas?

  Thanks in advance
  Skip

  Hello

  why Don t you are installing the system separately on the machine? Maybe it works. This thing with the IDE controller is true, but not the only story. There are things like the drivers and services that could possibly cause the BSOD.

  My suggestion: clean install with no problems and the drivers are present. That you please, ha? ;)

  Welcome them

• BSOD on Sysprep

  I am trying to sysprep my X 1 carbon and after you run sysprep while closing, I get a BSOD with a DRIVER_POWER_STATE_FAILURE. I checked the minidump with bluescreen viewer and the problem driver is listed as ntoskrnl.exe. No idea which driver might cause this?

  Link to photo/image

  Mod comment: Over size photo converted to establish a link. Please visit About-Posting-Pictures-In-The-Forums

  I got a reply on net microsoft technology. I submitted the memory dump, and it turns out that 3 usb driver was causing the problem. I had to uninstall and reinstall all my drivers usb Manager devices, just before you run sysprep. No BSOD after that.

• P300 drivers do not install sysprep

  We recently got a few P300s to add to our environment.

  The drivers for this device have been added successfully to our unified using DISM .wim image. After you apply the image to the P300, it goes through the usual process of sysprep and seems to be setting up the PC. However, it cannot join the domain and on logging as long as local administrator, he has in fact not all installed drivers P300.

  Strangely, if I simply launch a manual 'Search for hardware changes' in the Device Manager, all devices installed very well. If the driver files are present and functional, but for some reason any on his machine is not installed automatically. Another way I can start the installation, is going in the device settings and to update Windows Update (even if it's just using those found locally).

  I tried several ways to get this working, including "devcon rescan" running initially to the top, but nothing helped. In any case, they really need to settle during the sysprep process so that the ethernet controller install and he can join the domain correctly.

  I also tried to recreate the image from scratch, but the problem persists, even though I explicitally drivers only P300. If I manually install or follow my steps above of course, they work fine... I could take a picture with them installed and add the drivers of the other models, but it's not ideal.

  This problem will not occur on all other machines that we use this image, including many other models of Lenovo.

  
  

• Compaq Elite 8300 AIO: Blue screen on reboot of the system after sysprep

  After syspreping the computer to restart the computer, I have BSOD (blue screen) with the message:

  STOP: 0x0000007E (0xFFFFFFFFC0000005,...) without any additional information on the driver

  the image works perfectly before syspreping, I know that it is a driver issue, which should be removed after the generalize in the sysprep, I don't have a wireless network card

  Thank you!

  We always using ghost to deploy our image but we have different models, I always use the latest model that we receive to capture my image. The sysprep command is supposed to cleaning drivers and drivers from a defined location will apply depending on the model.

  without knowing the pilot originally, I tried to change the drive (from an operational model) but the same result, my graphics card is built into my motherboard.

  I solved the problem by replacing the folder: "c:------windows-system32-drivers" coming from an old image of operation.

  But I have to watch on my file sysprep to see why it does not consider my drivers folder and use than the windows folder

• Cannot start Windows Server R2 2012 after sysprep

  Hello!

  I wanted to create a complete picture of my operating system (Windows Server 2012 R2) with installed applications and configuration done, so I ran sysprep to prepare my system for Imaging. But I chose a reboot instead of the stop option option and now my system is unable to start. Basically it stuck on the location screen (with adjustment for keyboard and so on), when I click on 'Next' nothing happens, what I can see "apply these settings" but it looks like she never applies.

  What can I do to solve this problem without reinstallation of the system?

  P.S. I have no backup :( I know, it's really stupid and maybe my fatal mistake, but now it's a good lesson for me...

  Thanks in advance!

  This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)
  *
  http://social.technet.Microsoft.com/forums/en-us/home s/fr-U.S./Accueil
  http://social.msdn.Microsoft.com/Forum