-
Posts
314 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Events
Posts posted by alfreire
-
-
Well... I made a new test... I load next hives from Image mounted (Win 7 x64 Pro SP1 untouched Install.wim) in Regedit:
-C:\Users\Administrator\NTUSER.DAT
-C:\Users\Default\NTUSER.DAT
-C:\Windows\Sistem32\config\DEFAULT
In all hives I add to [software\Microsoft\CTF] the next value:
[LangBar]"ShowStatus"=dword:00000003
I made 2 test, one with Autounattend.xml (default user is Admin), and other with default User (without Autounattend.xml)... WORKS PERFECT...!!!
Regards... ;-)
-
I load NTUSER.DAT and DEFAULT (not DEFAULT.DAT) hives (from Mounted Image) in Regedit to manually add "ShowStatus"=dword:00000003 in [software\Microsoft\CTF\LangBar]...
Regards...;-)
p.d.: I think so Win Toolkit added reg data only to NTUSER.DAT, but not in DEFAULT wich it's for ADMIN USER (or DEFAULT USER)...
-
That means we must mount the image install.wim and use reg.exe to load the NTUSER.DAT to integrate the registry key inside the hive loaded:
http://www.msfn.org/board/topic/160244-registry-hive/page__view__findpost__p__1022499
That's what I've tried to say here ...
I found an solution time ago... Load NTUSER.DAT and DEFAULT hives (from Image Mounted) with Regedit, and edit with:
[software\Microsoft\CTF\LangBar]"ShowStatus"=dword:00000003
Regards...;-)
Regards... ;-)
-
About Windows6.1-KB2670838-x64.msu there is sometimes trouble and if it's the case try do not install this update:
http://www.winbeta.org/news/botched-update-kb2670838-windows-7-resulting-bsod-microsoft-working-fix
Thanks, friend...
Regards... ;-)
-
-
I found an solution time ago... Load NTUSER.DAT and DEFAULT hives (from Image Mounted) with Regedit, and edit with:
[software\Microsoft\CTF\LangBar]"ShowStatus"=dword:00000003
Regards...;-)
-
SuperTalent Express RC8 50Gb work without problem, I have one...
Regards... ;-)
-
With v1.5.0.1 I don't get error... (but one update don't integrate)
-
I got error with v1.4.1.15 &1.4.1.16 when finalized updates integration...
Dates:
Descripción:
Stopped working
Firma con problemas:
Nombre del evento de problema: APPCRASH
Application Name: WinToolkit.exe
Application Version: 1.4.1.16
Application Timestamp: 5133ea18
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.22178
Fault Module Timestamp: 50b99994
Exception Code: e053534f
Exception Offset: 000000000001a53d
Versión del sistema operativo: 6.1.7601.2.1.0.256.48
Id. de configuración regional: 3082
Lea nuestra declaración de privacidad en línea:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0c0a
Log:
[2164] Caller did not request sparse mount
[2164] Mounting new image.
Wim: [C:\temp6\Install.wim]
Image Index: [3]
Mount Path: [H:\WinMount]
[2164] Wimserv process started for guid 9123c0d8-a18e-4000-9627-c88903bf9fe3. Id is 3388
[3388] [ INFO ] ImageUnmarshallHandle: Reconstituting wim at C:\temp6\Install.wim.
[3388] [ INFO ] Mounted image at H:\WinMount.
*AIO
#Updates
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Additional\IE10\Prerequisites\Windows6.1-KB2670838-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Additional\IE10\Prerequisites\Windows6.1-KB2533623-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Additional\IE10\Prerequisites\Windows6.1-KB2729094-v2-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Additional\IE10\Prerequisites\Windows6.1-KB2786081-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2803759-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2803752-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2801453-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2800422-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2800789-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2800213-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2799406-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2800170-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2799360-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2799035-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2798787-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2798286-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2797918-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2797789-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2796647-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2796725-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2796313-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2794119-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2790817-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2790113-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2790804-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2789645-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2781049-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2780130-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2778344-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2693010-v2-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2732673-v3-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2524732-v2-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2591271-v2-x64.msu
C:\temp\Windows 7 Toolkit\McRip\McRip Windows 7 x64\Windows6.1-KB2459530-v4-x64.msu
#Options
Compatibility Check
Create Backups
Enable CMD
Integrate 'HDC' Drivers (boot.wim)
Integrate 'SCSIADAPTER' Drivers (boot.wim)
Integrate 'SYSTEM' Drivers (boot.wim)
Prepare Drivers
Prompt Addons
Prompt Drivers
Prompt Gadgets
Prompt Silent
Prompt Themes
Prompt Updates
Prompt Wallpapers
Rebuild Image
Show Browse Dialog
Show DuplicatesRegards...;-)
-
Hi,
lets Bomb the Sandisk Forum together?
Greetz X23
Hehehehe, well-done... :bomb: to see if they respond... :help:
Regards... ;-)
-
Hi,
i can confirm it's a must to pull the Sandisk USB 3.0 Extreme while partition choosing, then refresh, put in again, another refresh and its possible to install to the hdd.
Nasty Workaround but i works. I want to fix that! but how?
Greetz X23
I want to fix also...
Regards... ;-)
-
Hi,
lets say the stick is detected as sata hdd and not as usb stick itselfs, how is the priority from windows setup
to set this or that decive infront of the internal disk list? (sorry i dont know how to spell that better).
we can test that with booting from dvd while the usb stick is connected. I can do this tomorrow at work.
Maybe it is a priorisation for usb 3.0 devices (regardingless they are connected to usb 3.0 or 2.0) before interal sata devices.
Well, but with other USB 3.0 devices work without problem... perhaps the reason it's by construction of Sandisk stick, I think i's a SSD stick...
Regards... ;-)
-
The only reason to reconnect the stick an then it works is that setup trys to install bootloader to sandisk instead of hdd that is choosen.
Yes, that it's correct... but I don't know why...
Regards... ;-)
-
Hehehehe... I have the same problem with Sandisk Extreme 64Gb...but I found a solution...
When you see this image to choose partition:
Unplug stick from USB and click Refresh button... Insert stick on USB and click again in Refresh button, now create partition and install... works for me...
Sorry for my bad english... X-D
Regards... ;-)
This method work perfect... I not need use this method with other USB 3.0 pendrives... I have Kingston DataTraveler Ultimate G2 32Gb and Supertalent Express RC8 50Gb, and work perfect with same files and hardware...
Regards... ;-)
-
had the same problem! USB 3.0 Sandisk Extreme 16GB,
it worked as wiktorynka said!
The only solution:
Insert the flash drive Sandisk Extreme 3.0 on installation time to a USB
2.0 port and will not be a problem. The problem is missing drivers for
the USB 3.0 controller before installing the system is not in the image
of the system. Problem is not the stick.
The problem is Sandisk Extreme 3.0... If I copy all files from Sandisk Extreme 3.0 to other USB 3.0 stick, Windows 7 install work perfect in USB 3.0...
Regards... ;-)
-
Use only right drivers for you hardware... you can backup your hardware drivers from Windows to integrate in boot.wim...
Regards... ;-)
p.d.: I use Drivers Backup Solution to get drivers from Windows... http://www.adia-project.net/news/43-dbs-drivers-backup-solution-v3921-stable-beta.html
-
Hi,
i've a image where are a bunch of drivers integrated (Chipset, lan, wlan, cardreader, mass storage) about 660,
i've checked the option to integrate drivers to the boot.wim and made a new image but boot.wim is untouched nothing changed it just rebuilded the install.wim
So the question is is it needed to always load the drivers preset althougth i allready integrated them... at this time i didnt reload the drivers presets because iam afraid it reintegrates the driver while i allready did it (i hate to wait so long).
So what is the right way to have the drivers integrated into the boot.wim?
Must the the option been checked while iam going to integrate drivers the first time?
I hope not the last case is needed else i have to reintegrate the drivers all again...
Greetz X23
I mount only boot.wim in WinToolkit to add USB and MassStorage drivers... works perfect...
Regards... ;-)
-
Hi,
first i tried with wintoolkit and the sandisk didn't boot.
then i tried the microsoft tool to create a usb stick, with that it boot but now i have a another mistake.
Setup will find all hdds but will not install to any of it the error message is:
I have to translate from german to english by myself...
Setup cannot create a new system partition or find an existing partition to install to...
But i see all the harddisks and i also can create or delete partitions on them but if i choose one
partition to install to i get the error message above... Damn i shouldn't bougth a usb 3.0 i should took a usb 2.0 one.
What a bull****... (related to usb 3.0)
I do the same procedure with an usb 2.0 stick anything works.
Greetz X23
Hehehehe... I have the same problem with Sandisk Extreme 64Gb...but I found a solution...
When you see this image to choose partition:
Unplug stick from USB and click Refresh button... Insert stick on USB and click again in Refresh button, now create partition and install... works for me...
Sorry for my bad english... X-D
Regards... ;-)
-
Thanks, Rick... ;-)
-
...and Happy New Year...!!! :guitar:
-
Glad your back, Lego...
Regards... ;-)
-
Thanks, Rick... :beerchug:
Regards... ;-)
-
Try %USERPROFILE%\Documents\test.doc
Regards... ;-)
-
Do this, it's real simple and clean. Download Double Driver, backup your live system drivers, and DD will organize all your current (Live) drivers and in a nicely designated target directory/folder of your choice. The only thing left to do after that is integrate what you backed up in the drivers tab of Win Toolkit. If you have any questions, doubt or concerns, just reply to this thread and I'll fill in the gabs if I can.
Thanks by your answer... Double Driver it's a good Free program...
Regards... ;-)
Language Bar
in Win Toolkit
Posted · Edited by alfreire
I'm glad... Sorry that I did not explained well before, my English is not very good... X-D
Regards... ;-)