If genuine OEM, the user can activate it for him/herself. OK. I'll download it and see if he brought us GVLK key.
You might run into script errors if using >nul 2>&1 to nul the errors out...I have found that vista and win 7 need powershell installed which also requires .net 4.5 for >nul 2>&1 to nul correctly. Reason being is the & without powershell will be seen as next line of code which a 1 follows so script might error. I created a lil project that I made work on vista-win8.x (not related to anything here) that had this exact problem but powershell allowed the >nul 2>&1 to work like it should. Not saying you are receiving errors but something you might want to look closer at just for GP.
This? Code: wpeutil.exe WaitForRemovableStorage >nul 2>&1 wpeutil.exe UpdateBootInfo >nul 2>&1 Thank you. Actually I am not educated, but put together what I found.
2>nul should work if normal >nul doesn't...try and see is my only advise. I was just sharing something that caught my eye. lol I have had issues with >nul 2>&1 on vista and win 7 only....win 8.x comes with powershell enabled by default so no issues there. Sorry, I didn't mean to butt in but like I said I seen something that caught my eye is all. lol
Can't you use findstr for that? Just trying to understand what you are wanting to do. Ok, I seen you edited your post so I understand better but I cant answer the last two questions. I would like to know how and when windows gets the key and applies it but I haven't found that info anywhere yet. Think my helping is done for the evening. lol I wish I could answer the other questions but I can't.
Yes I did if it was in one line. But ... being so complicated. No. I cannot. Code: OEM Activation Tool 3.0 (c) Copyright 2011 Microsoft Corp. Version: 6.3.9600 The ACPI MSDM table: 4d 53 44 4d 55 00 00 00 03 71 44 45 4c 4c 20 20 50 45 5f 53 43 33 20 20 00 00 04 06 41 53 4c 20 00 00 04 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 1d 00 00 00 42 48 33 52 4e 2d 42 37 46 44 4d 2d 43 37 57 47 54 2d 34 43 52 34 58 2d 36 43 4b 48 4d The ACPI MSDM data : Signature: MSDM Length: 85 (0x55) Revision: 3 CheckSum: 0x71 OEMID: DELL OEMTableID: PE_SC3 OEMRevision: 0x6040000 CreatorID: ASL CreatorRev: 262144 The ACPI MSDM table in hex: 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 1d 00 00 00 42 48 33 52 4e 2d 42 37 46 44 4d 2d 43 37 57 47 54 2d 34 43 52 34 58 2d 36 43 4b 48 4d ACPI MSDM table payload: Version: 1 Type: 1 DataLength: 29 Partial Product Key: 6CKHM