Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Search the Community

Showing results for tags 'Windows 10'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server 2008/2012/2016
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL





Found 57 results

  1. Tihiy

    StartIsBack++ 2.7

    Please welcome on the stage again: the Start menu which refused to die! StartIsBack++ is the all-new StartIsBack version for Windows 10. What's hot about StartIsBack on Windows 10 now? - Full taskbar skinning! - Jumplists replacement! - Dark Mode support! - Ability to reduce resource usage by disabling newer Start menu and Cortana processes from prelaunching - Ability to use adequately sized (32x32) large icons and larger start menu button on taskbar - Modern icon glyphs on Start menu right hand pane - Modern blur, drop shadow and immersive context menus for start menu - Fully dynamic DPI aware start menu and configuration app - New modern style with round user picture - Lots of new minor additions and tweaks
  2. xarzu

    Windows 10 Update Issues...

    I got locked in one of those update loops. You know what I mean, probably. My Windows 10 would start an automatic update, then fail, and then reset itself to a previous version. This would happen all of the time. I managed to use one of the methods on this link to successfully do an update: https://www.alphr.com/microsoft/1001411/how-to-fix-windows-update-in-windows-10-if-it-becomes-stuck-1 Now, here is the reason why I am making this post. In case I want to ever do a completely fresh reinstall of Windows 10, I want to know how to do this because the CD (DVD, maybe?) and all I have is the ("OEM"?) sticker with the associated ID numbers.
  3. Go direct to new description including Windows 10 Install Windows 10 from USB After Booting with WIM or VHDX https://msfn.org/board/topic/121446-install-from-usb-after-booting-with-pe/?do=findComment&comment=1155026 ================================================================================ Install of XP or Windows 7 from USB After Booting with 7 PE and by using WinNTSetup2_x86.exe and Setup ISO file in Virtual drive 0. Use BOOT_USB.exe to prepare USB or HDD drive for booting with Grub4dos Menu and using 7 PE Boot Image file - Info BOOT_USB - http://www.911cd.net/forums//index.php?showtopic=24424 - Info Make_PE3 - http://www.911cd.net/forums//index.php?showtopic=23931 1. Boot from USB or HDD with 7 PE loaded in RAMDISK - use Grub4dos Boot Menu and 7pe_x86_E.iso Boot Image file 2. Use R-mouse to Mount Windows Setup ISO in ImDisk virtual drive - If needed first Install ImDisk driver by running imdiskinst.exe (also available in makebt folder) 3. Quick Format TargetDrive - use NTFS FileSystem 4. Run WinNTSetup2_x86.exe and prepare Target drive for Install of XP or Windows 7 Thanks to JFX - http://www.msfn.org/board/topic/149612-winntsetup-v2/ 5. Reboot from Target Drive and Install XP or Windows 7 Instead of 7 PE you can use any other way of booting that allows you to Format and prepare your Target Drive. You might decide e.g. to boot with Portable Windows XP IMG or with Windows 7 VHD from USB In any case you can use WinNTSetup2_x86.exe to prepare your Target drive for Install of XP or Windows 7 See Tutorial file XP-W7-Setup.txt in IMG_XP\Help_Info folder Info IMG_XP - http://www.911cd.net/forums//index.php?showtopic=23553 Download - End of Support The advantage is that you never boot from USB during XP Setup and that makes everything much more reliable and you have full control of what you are doing. Also using a single XP Setup ISO file mounted in ImDisk Virtual drive is much more reliable than having a bunch of XP Setup files on USB. Transfer of the ISO file to USB is much faster and easier to maintain. Instead of USB-stick it is much better to use Portable 2.5 inch USB-harddisk e.g. Samsung S2 As easy to carry and connect, but much higher speed and more capacity. ================================================================================ old approach with useful info left here for reference *** Install from USB AFTER Booting with PE *** Install from USB without Booting from USB by using U_XP_SET ================================================================================ 0. Introduction Install of XP from USB involves: Boot in 30 seconds with LiveXP Boot Image from RAMDISK loaded in few seconds from HD (preferred) or from USB in 5 minutes Run USB_XP_Setup.exe and select and Quick Format your Target Drive on which you want to Install XP Select your XP Setup Source folder and LiveXP Boot Image file and use GO to prepare Target Drive for Install of XP Reboot Computer from Target Install Drive and Select XP Setup from boot.ini Menu Proceed as usual with TXT-mode and Reboot for GUI-mode of Unattended XP Setup To perform the above requires some preparation: Prepare XP Setup Source Folder and Live XP Boot Image file as described in Tutorial in Sections 2 and 3 Use Make_USB.exe so that your USB-stick or USB-Harddisk contains XP Setup Source folder and U_XP_SET folder and LiveXP Boot Image file Run BOOT_IMG.exe to Install LiveXP Boot Image file as boot option on C-BootDrive of Harddisk For blank HDD you need to create first an Active Primary NTFS partition: Use Make_USB.exe to make USB-stick having XP Setup Source and being bootable with LiveXP Use BOOT_IMG.exe to make USB-stick also bootable with Parted Magic 4.6 (See Section 6) After booting from USB-stick with Parted Magic from GRUB4DOS menu, you can create Primary NTFS partition using GParted Reboot from USB-stick with LiveXP PE and Set Active the created Primary NTFS partition using Disk Management In LiveXP you must fix the MBR of your HDD using MBRFix.exe (in makebt folder), since Parted Magic will not create the required MBR bootcode to make drive bootable If your HDD is drive 0 then in cmd window opened at makebt folder run: MbrFix /drive 0 fixmbr Run USB_XP_Setup.exe to Quick Format TargetDrive and prepare HDD for Install of XP Reboot from HDD for Install of XP and continue as usual with TXT and GUI mode of XP Setup (change BIOS settings to boot from HDD if needed) ================================================================================ 1. Install of XP using USB_XP_Setup.exe The package U_XP_SET contains Folder USB_XP_Setup with 3 Programs, which you can Launch via PStart.exe Menu Make_USB.exe can Copy your XP Source to USB-Drive and can make it Bootable with LiveXP for Emergency BOOT_IMG.exe Copies WinBuilder LiveXP Boot Image file to C-Harddisk or USB-Drive and makes Entry for boot.ini Menu and GRUB4DOS menu.lst for Booting with LiveXP PE from RAMDISK. This is useful as Escape Boot Option in case Booting with Windows XP or XP Setup may fail, so that you can Repair your System or use Ghost for System Backup and System Restore. USB_XP_Setup.exe can make XP Setup BootFolder $WIN_NT$.~BT on Install-Drive usually C: and will specify in TXTSETUP.SIF where to find the FULL XP Source on partition 1 of USB-Stick. For all other cases of Install of XP e.g. from any Harddisk folder or Network Shared folder or from CD / DVD disk, then the XP Source is always Copied to $WIN_NT$.~LS folder on Target Install-drive. Before you Start to Install XP: Prepare XP Source Folder and Live XP Boot Image File as described in Sections 2 and 3 Vista as OS requires to turn User Account Control OFF (only needed for the old Batch cmd Programs) Run the SFX SelfExtractor U_XP_SET.exe and use Extract to the Root of your Workstation Harddisk In this way you will get on your Local Harddisk the folder U_XP_SET with PStart.exe to launch the 3 Programs Copy Winbuilder\Workbench\Common\BootSDI\setupldr.bin and ramdisk.sys to USB_XP_Setup\makebt\srsp1 folder Run Make_USB.exe and Select and use as Target Drive a FAST USB-stick (e.g. Corsair Flash Voyager 4-8 GB) Use Format Stick button or HP Format Tool to format Target USB-stick with NTFS FileSystem (Fastest for FileCopy) Select your XP Source Folder and LiveXP Boot Image File and Enable Copy of U_XP_SET Folder to Make your USB-stick Run BOOT_IMG.exe to Copy WinBuilder LiveXP Boot Image file to C-BootDrive of Harddisk and make Entry for boot.ini Menu and GRUB4DOS menu.lst for Booting with LiveXP PE from RAMDISK. This is also useful as Escape Boot Option in case Booting with Windows XP or XP Setup may fail, so that you can Repair your System or use Ghost for System Backup and System Restore. The XP Setup Procedure for Fresh Install of XP: Connect USB-Stick having XP Source in partition 1 (Connect before Booting with LiveXP from HDD) or use any other XP Setup Source. Remove All Other USB-Drives like CardReaders and USB-Harddisks Reboot from C-Harddisk and Select to Boot from RAMDISK with LiveXP into PE Environment Run USB_XP_Setup.exe and Quick Format with NTFS your Selected Target Install-Drive usually C: Use GO to make XP Setup BootFolder $WIN_NT$.~BT on Target Install-Drive. First give XP Setup Source Path and give LiveXP RAM BootSDI IMAGE File. So in case when XP Setup fails, you have LiveXP as Escape Boot Option available on your Fresh Formatted Install Drive. XP Source not on USB-stick is always Copied to $WIN_NT$.~LS folder on Target Install-drive. If you Install on other than Active C-drive, then Use Disk Manager to Activate Install Drive Partition Reboot Computer from Install Drive and Select XP Setup from boot.ini Menu Proceed as usual with TXT-mode and GUI-mode of Unattended XP Setup In TXT-mode after FAST loading drivers the blue screen becomes black and then one needs to wait sufficiently until the blue screen with the Drive Partition List appears. Select the Install Partition usually C: and Auto proceed with FileCopy and Reboot for GUI-mode of XP Setup. WARNING Don't Delete the Install Partition, just Install on this previously in PE Quick Formatted NTFS Partition. Changing the Partitioning is a task which is done in LiveXP PE Environment with 7Tools Partition Manager 2005 of Paragon ( Preferred ) or Acronis Disk Director 10. The advantage of the present technique is that there are no changes needed in the BIOS Setting. Booting for XP Setup occurs all the time as normal from the C-Install Drive if you Install on C-Drive. Thus the USB-stick does not need to be bootable and it is not needed that the motherboard supports booting from USB. In the case of total computer disaster it can still be handy to boot with LiveXP from USB-drive. Another advantage is that you can use the FULL XP Source unchanged just as with Install from CD and the $OEM$ folder is recognised and the [unattended] section of winnt.sif file is used as normal. Moreover USB_XP_Setup.exe allows to Select from different XP Sources on USB-Drive to be used for XP Setup. Supports the use of BTS DriverPacks located in OEM Folder in XP Source Folder on USB-Drive http://driverpacks.net/downloads Install XP from USB AFTER booting with PE does not make use of WINNT32.EXE In fact the only thing I do is Create the XP BootFolder $WIN_NT$.~BT of only 12 MB on the Install Drive by parsing dosnet.inf and to specify in TXTSETUP.SIF where to find the FULL XPSOURCE. In this case the XP Setup Source Folder must be on USB-stick. For all other cases of Install of XP e.g. from any Harddisk folder or Network Shared folder or from CD / DVD disk, then the XP Source is always Copied to $WIN_NT$.~LS folder on Target Install-drive. Thanks to ilko_t I have learned how to use SetupSourcePath and SetupSourceDevice to specify in TXTSETUP.SIF where to find the XP Source Folder, thus enabling Alternative location of Setup files when installing from HD media http://www.msfn.org/board/Alternative-loca...en-t119742.html ================================================================================ TXT-mode XP Setup Error in case of Install of XP with Setup Source on USB-stick TXT-mode Setup Memory/CD-Error means harddisk nr in SetupSourceDevice is incorrect Solution: - ReBoot with LiveXP Boot Image from RAMDISK, Run PStart and run again USB_XP_Setup.exe - Now Select Copy XP Setup Source Folder to Target Drive folder $WIN_NT$.~LS - Reboot Computer from Install Drive and Select XP Setup from boot.ini Menu Possible causes of TXT-mode Setup Memory/CD-Error are: - Change of Harddisk Numbering by BIOS due to Hardware Configuration Change on Reboot. Try to disconnect ZIP-drive, Cardreader or use different USB-port. - Change of Harddisk Numbering by BIOS due to connecting USB-drive AFTER Booting with PE or XP XP Setup may fail - due to XP Source Harddisk Number Change on Reboot In this case Reboot with LiveXP PE and USB-drive CONNECTED to Reset Harddisk Number Run USB_XP_SETUP.cmd again to get correct SetupSourceDevice in TXTSETUP.SIF - Inconsistent Harddisk Numbering by BIOS caused by Incompatible type of USB-stick - Intuix 8 GB - Old BIOS versions, where harddisk number of USB-Drive and Install Drive are Reversed in TXT-Mode and GUI-Mode You can Use Disk Manager Manually to determine Harddisk Numbers and use Notepad to correct harddisk nr and XP SOURCE Folder in TXTSETUP.SIF [setupData] SetupSourcePath = "\XPPRO\" SetupSourceDevice = \device\harddisk1\partition1 In this case change file %instdrive%\txtsetup.sif and %instdrive%\$WIN_NT$.~BT\txtsetup.sif ================================================================================ How to boot with LiveXP from Harddisk using extra option in boot.ini Menu was described by me in http://www.911cd.net/forums//index.php?sho...21682&st=24 Combining this technique with the possibility to make XP Setup BootFolder $WIN_NT$.~BT on C-Install-Drive by parsing dosnet.inf and to specify in TXTSETUP.SIF the XP Source location on USB-stick has resulted in this way of Install of XP from USB-stick AFTER booting with PE from C-Harddisk. In LiveXP you can Connect to Network Drive using PENetwork Manager with Path: \\ComputerName\ShareName User: ComputerName\UserName Pass: PassWord It might be necessary to switch off the Firewall of the Network computer. Network Shared Folders can also be used as Source folder in USB_XP_Setup.exe and Make_USB.exe For Install of XP in a folder e.g. WIN51 next to existing WINDOWS folder or for Repair Install you can use USB_XP_Setup.exe direct from HDD without booting first into PE Environment. Repair Install using USB_XP_Setup.exe XP Setup Source Folder can be on USB-stick or anywhere else. Connect USB-stick having XP Source in partition 1 Remove All Other USB-Drives like CardReaders and USB-Harddisks Reboot as NORMAL from C-Harddisk, so that BIOS Resets USB-drive number Run USB_XP_SETUP.exe to make XP Setup BootFolder $WIN_NT$.~BT on Install-Drive usually C: Repair Install is enabled by Disabling [unattended] Section using ; in C:\$WIN_NT$.~BT\winnt.sif file Reboot Computer from Install Drive usually C: and Select XP Setup from boot.ini Menu Select in TXT-mode Existing Windows for Repair and continue with GUI-mode of XP Setup ================================================================================ 2. XP-Source Preparation Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES. Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk Slipstream ServicePack SP3 First Manually in your XP-SP2 Source (don't use here nLite). http://www.helpwithwindows.com/WindowsXP/S...ice_Pack_3.html Siginet's RyanVM Integrator or nLite can then be used to Integrate Windows UpdatePacks in the XP-Source. Preferred is using RyanVM Integrator 1.6 - http://integrator.siginetsoftware.com/index.php?download Or Alternatively use nLite to Integrate Windows UpdatePacks http://www.nliteos.com/ Windows XP UpdatePacks and Addons: http://www.ryanvm.net/msfn/ http://www.ryanvm.net/msfn/updatepack-sp2.html http://integrator.siginetsoftware.com/index.php?addons http://www.ryanvm.net/forum/ Supports the use of BTS DriverPacks located in OEM Folder on USB-Drive http://driverpacks.net/downloads For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled. In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems. It will be useful to Add also Chipset, CPU and LAN DriverPack, which are small so that the decompression at the beginning of GUI-mode of XP Setup does NOT take to much time. Always first use RyanVM Integrator or nLite and then use DPsBase to Improve your XP-Source. The program supplies a Customised presetup.cmd and changes the winnt.sif file for use of DriverPacks. When you don't use nLite, you can copy the supplied $OEM$ folder to your XP Source folder. Change $OEM$ folder to your needs for UserAccounts and Registry Tweaks and Adding Drivers. CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12 Info see: http://unattended.msfn.org/unattended.xp/ PnP Drivers specified in winnt.sif can be added to $OEM$\$1\Drivers http://unattended.msfn.org/unattended.xp/view/web/34/ TEXTMODE Drivers defined in winnt.sif and located in $OEM$\TEXTMODE folder of the XP Source can be used instead of using F6 floppy for MassStorage Drivers. The content of the $OEM$\TEXTMODE folder is copied by USB_XP_Setup.exe to XP Setup BootFolder $WIN_NT$.~BT\$OEM$ See cdob and allanf in http://www.boot-land.net/forums/index.php?...5306&st=180 Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP. http://www.911cd.net/forums//index.php?showtopic=20555 The complete XP-Source can be copied by Make_USB.exe to USB-Drive. Computation of Estimated XP Folder Size is used to prevent USB-stick overflow and includes cmpnents + I386 + AMD64 + $OEM$ + OEM Folders. Excluding LANG and WIN98X Folders from Copy to USB is the Default Setting in Make_USB.exe Main Menu, which reduces the XP-Source on USB-Drive by 135 MB ================================================================================ 3. LiveXP Boot Image File Preparation Download LiveXP e.g. lx77rc2cxw.exe from folder Projects or lx77rc2cbw.exe from folder Portable http://amalux.winbuilder.net/ Run the downloaded exe and extract to simple path without spaces e.g. extract to root of your local harddisk. You can add a Ghost script (Ghost Plus!.script) which is very handy for System Backup and Restore. Copy file Ghost Plus!.script from http://amalux.winbuilder.net/index.php?dir=MyScripts/Backup/ to <WinBuilder>\Projects\LiveXP\Apps\System folder For making LiveXP Boot Image file you need original XP-SP2 or XP-SP3 Setup CD copied to folder in root of harddisk. Use simple name without spaces for XP Setup Source folder and Switch Off your Firewall and AntiVirus protection. The MassStorage DriverPack for support of SATA drives is automatically integrated in LiveXP made with WinBuilder. In case of WinBuilder Errors use Button Clean Temporary Files in Advance. On Success Save WinBuilder Settings with WB Manager useful later for Restore of Settings. Run WinBuilder to make in 15 min your LiveXP_WIM.ISO or LiveXP_RAM.ISO Boot Image file in folder <WinBuilder>\ISO Alternatively you may use BootSDI.img file made in folder <WinBuilder>\ISO\Ram\I386 ramdisk.sys and setupldr.bin of Windows Server 2003 SP1 must be in <WinBuilder>\Workbench\Common\BootSDI directory. Activate Finish > Create Image > Boot SDI and Run WinBuilder. You can Deactivate Emulation and Burn Image, since we don't need a CD for our purpose. IMG-type files can be changed afterwards more easily by simply mounting them in Virtual Drive with R-mouse using ImDisk or with VDK. Run makebt\Mount_IMG.cmd and Select to Mount your BootSDI.img file in a Virtual Drive using VDK Copy your add-ons to your Virtual Drive in which you mounted BootSDI.img file Use UnMount_IMG.cmd to Close the Virtual Drive and Save the Changes in your BootSDI.img file FileName of IMG or ISO files for loading into RAMDISK, like LiveXP BootSDI.img file, must be conform DOS 8.3 because otherwise in case of FAT or FAT32 Filesystem you would get Error 14 (File Not Found). Tutorial of amalux on how to create LiveXP Boot Image files using WinBuilder http://www.boot-land.net/forums/?showtopic=4111 ================================================================================ 4. Install of Drivers and Programs Automatic Install of Drivers during XP Setup 1. Using 7-Zip Compressed DriverPacks located in OEM Folder on USB-Drive, which are decompressed by presetup.cmd at beginning of GUI-mode of XP Setup. http://driverpacks.net/downloads For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled. In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems. First use RyanVM Integrator and then use DPsBase to Improve your XP-Source. The program supplies a Customised presetup.cmd and changes the winnt.sif file for use of DriverPacks. 2. Using DriverForge.v4.5.4.exe to Install from C:\Drivers at T-9 of GUI XP Setup (just for the last Reboot). DriverForge.v4.5.4.exe made by kickarse http://www.msfn.org/board/index.php?showtopic=110783 At end of TXT-mode XP Setup the folder $OEM$\$1\Drivers is copied to C:\Drivers and $OEM$\$1\Install\DriverForge.v4.5.4.exe is copied to C:\Install When you don't use nLite, you can Copy the supplied USB_XP_Setup\$OEM$ folder to your XP Source folder. For Auto Use of DriverForge at T-9 you can place uncompressed drivers (or folders) in Drivers of $OEM$ and then Uncomment two rules by removing ; in U_XP_SET\USB_XP_Setup\w_sif\winnt.sif file (see below). You can also change driverforge.ini to your needs if you want to use drivers on a different location, or you may even use the compressed DriverPacks. [setupParams] UserExecute = "%SystemDrive%\INSTALL\SetupPar.cmd" Method 2 can be very fast because you can just use in Drivers your well known set of required drivers. The ATI Catalyst Control Center can be Installed separately with other Apps After Setup has completed. Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP. http://www.911cd.net/forums//index.php?sho...20555&st=69 ================================================================================ Install of Programs After XP Setup has finished It is handy to use the Office Integrator of Siginet and benners to Integrate Service Packs and HotPacks before installing Office. http://www.siginetsoftware.com/forum/ Download Office Integrator v1.1 Build 16 http://integrator.siginetsoftware.com/inde...dons&id=213 The Folder usb_cfg_extra provides a script for Windows Post-Install Wizard (WPI) - http://wpiw.net/ WPI is very handy for the Automatic Install of Programs after Install of XP from USB. Some Tweaks are done at best when XP Setup has completed e.g. the IE7_Tweaks and NoWallpaper So I combine these tweaks with the Install of Apps using WPI and launch WPI Manually AFTER logon and when the XP Desktop is ready. As example a config.js script is provided in U_XP_SET\USB_XP_Setup\usb_cfg_extra\INSTALL_PRGS_WPI\WPIScripts In WPI script there is the option to run SFC /purgecache which deletes the dll cache by deleting the files in Folder C:\WINDOWS\system32\dllcache This is a very simple way to reduce the WINDOWS Folder Size by 360 MB The Result is a XP WINDOWS Folder Size on Harddisk of only 900 MB inclusive all Updates. Install of XP from USB including Drivers with DriverForge and Post Install using WPI for the Apps is realised Now within 30 minutes using USB-stick with NTFS Format. ================================================================================ 5. Install Vista from USB Procedure for Install of Vista or Windows 7 from USB-stick Download and Extract U_XP_SET package making U_XP_SET folder on your Harddisk Launch PStart.exe in U_XP_SET folder Run BOOT_IMG.exe from PStart Menu to Install Windows PE 2.1 ISO as GRUB4DOS Boot Option in menu.lst Menu on Harddisk Boot Drive e.g. C:\ Reboot in 40 sec with Windows PE 2.1 ISO loaded by GRUB4DOS from HD into RAMDISK X: Run Vista Setup from folder on USB-stick by using e.g. Free Commander in PE 2.1 Environment Select and Format your Install Drive e.g. C:\ Proceed with Install of Vista from USB (Copy + Extract) Disconnect USB-stick precisely at First Reboot (just at the BIOS Beep when the screen is black). Without Removal there is 10 min Extra Install time. Proceed with Install of Vista - Totally in about 18 min The present approach is Install of Vista from USB without booting from USB. So you don't need BIOS USB Boot Support and you don't need to change BIOS Settings. Moreover, Vista Setup Source can be located in a folder on USB-stick so that it does not interfere with other Setup Sources like folders with Vista x64 or Windows 7 Setup Source. Thanks to jaclaz for Help with GRUB4DOS menu to boot with Windows PE 2.1 ISO file. Thanks to allanf for making WinBuilder Project to make Windows PE 2.1 ISO having GUI interface http://www.boot-land.net/forums/index.php?showtopic=7053 Download WAIK 1.1 Vista SP1 from http://www.microsoft.com/downloads/details...;displaylang=en Booting in 40 sec with pe21.iso loaded by GRUB4DOS from HD into RAMDISK X: allows then to Launch Vista or Windows 7 Setup.exe from folder on USB-stick. http://www.boot-land.net/forums/index.php?...=6800&st=37 Instead of Windows PE 2.1 we can also use VistaPE ISO, but booting with VistaPE will take several minutes. http://www.boot-land.net/forums/index.php?showforum=51 ================================================================================ Windows PE 3.0 ISO Boot Image With PStart Menu for Portable Programs Universal PE Booting from RAMDISK for Rescue and Install of XP or Windows 7 ================================================================================ Making Windows PE 3.0 ISO using AIK for Windows 7 Requirements The Windows Automated Installation Kit (AIK) for Windows 7 WLAN HotFix file Windows6.1-KB972831-x86.cab Installed Windows 7 to supply files to improve Windows PE 3.0 Program Make_PE3.cmd to make in 2 min your pe3.iso Boot Image in folder C:\winpe3_x86 Step 1. The Windows Automated Installation Kit (AIK) for Windows 7 Download KB3AIK_EN.iso from HERE Use ImgBurn or Nero to Burn the ISO Image on DVD Install Windows AIK according to: In case of Windows 7 Set User Account Control Off or use R-mouse Menu to Run as Administrator Run STARTCD.EXE from the AIK DVD In case of XP as OS - Install .NET Framework 2.0 In case of XP as OS - Install MSXML 6.0 Install Windows AIK Download WLAN HotFix from http://support.microsoft.com/kb/972831 Extract the HotFix to get file Windows6.1-KB972831-x86.cab Copy your HotFix file to folder WinPE_OCs made in Windows AIK\Tools\PETools\x86 folder. C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\Windows6.1-KB972831-x86.cab Step 2. Get Program Make_PE3.cmd to make pe3.iso Download - End of Support Run the SFX SelfExtractor Make_PE3.exe and use Extract to the Root of your Workstation Harddisk. The folder Make_PE3\PE3_mod contains file WIN7_Files.txt and 4 folders: PE3_add - Add your extra non-driver files in subfolder x86 structured as in Windows PE 3.0 PE3_reg - x86 subfolder contains 3 predefined Registry files with Windows 7 settings to improve the Registry of Windows PE 3.0 WIN7_add - Files needed from Installed Windows 7 are collected by the program in subfolder x86 WIN7_drivers - Add your Driver files e.g. for WLAN in folder x86 (recurse scanning allows subfolders with driver files) The actual filelist used by the program to get files is the generated WIN7_add_files.txt copy in folder WIN7_add\x86 In case of 64-bits Operating System then everywhere folder amd64 is used instead of x86 so that 64-bits can have its own list of files. For 64-bits Operating System you have to make similar registry files from your own Windows 7 Registry. Step 3. Run Make_PE3.cmd as Administrator to Create Windows PE 3.0 ISO pe3.iso of about 155 MB has been created in 2 minutes in folder C:\winpe3_x86 Working Directory Folder C:\winpe3_x86 is Created if it does not exist. File winpe.wim remains unchanged and is copied as file boot.wim to folder C:\winpe3_x86\ISO\sources The boot.wim file is mounted by imagex.exe in folder C:\winpe3_x86\mount Files from WIN7_add\x86 and PE3_add\x86 are added to mount by xcopy.exe, Packages and Drivers are added by Dism.exe The PE3 SYSTEM and SOFTWARE Registry files are improved with Windows 7 Settings using reg import Then imagex.exe will Unmount and Commit changes in boot.wim And finally oscdimg.exe will create the pe3.iso file in folder C:\winpe3_x86 Folders WIN7_add\x86 and AIK_Tools are generated and stay ready for future use. WARNING: In Windows 7 OS not using as Administrator results in Errors, because using imagex.exe reg.exe and dism.exe is Not allowed by User Account Control. If you made this mistake, you need before the next run to empty folder C:\winpe3_x86\mount Step 4. Install pe3.iso as GRUB4DOS boot option on HDD or USB Use BOOT_IMG.exe to Install pe3.iso of about 155 MB as GRUB4DOS boot option on HDD or USB Copy folder PStart or U_XP_SET to Root of HDD or USB drive to provide PStart Menu for portable programs. Download ppApps_Base!.exe from amalux for a nice collection of Portable Programs. http://amalux.winbuilder.net/index.php?dir=Portable%2F Add additional Portable Programs to folder Progs in folder PStart. Use PStart > Edit > Add file to modify PStart Menu. GRUB4DOS menu.lst entry title Boot pe3.iso - ISOfind --set-root --ignore-floppies /pe3.isomap /pe3.iso (0xff)map --hookroot (0xff)chainloader (0xff)/BOOTMGR Step 5. Reboot with pe3.iso from GRUB4DOS Menu on HDD or USB Boot with 155 MB pe3.iso in 30 sec from HDD or in 4 min from USB-stick. Use MultiRes from PStart PE3 System Menu to adjust the Screen Resolution to 1024 x 768 pixels Using ImDisk Install allows to use mounting e.g. XP Setup ISO in a in a Virtual Drive If desired, Run CmdHere to add Command Prompt Hereto the R-mouse context menu. Step 6. Install of XP or Windows 7 AFTER booting with pe3.iso If your XP Setup Source is an ISO file, then first install ImDisk driver so that you can mount the ISO in a virtual drive. Use PStart > Edit > Add file to select imdiskinst.exe from U_XP_SET\USB_XP_Setup\makebt folder and Run to install ImDisk driver. Then Launch Notepad from cmd window or from PStart Menu. In Notepad Select File > Open to get the FileSelector which can be used as File Browser for All Files. Then with R-mouse on the ISO file you can use the ImDisk context menu to mount the ISO in a Virtual Drive. If your Setup Source is a folder on HDD or USB or a CD/DVD drive then you don't need to use ImDisk. Launch USB_XP_Setup.exe from PStart Menu to prepare your Target drive for Install of XP. Info USB_XP_Setup.exe of U_XP_SET package http://www.911cd.net/forums//index.php?showtopic=21883 Launch NT6.X fast installer from PStart Menu to prepare your Target drive for Install of Windows 7. Info NT6.X fast installer of fujianabc http://www.boot-land.net/forums/index.php?showtopic=10126 Mounting XPSETUP.ISO in ImDisk Virtual Drive = = Windows PE 3.0 with PStart Menu for Portable Programs and having Browse for Folder Support = = Windows PE 3.0 with Partition Manager and Internet - Opera Portable and PENetwork.exe = = Windows PE 3.0 with PStart Menu for PE3 System and for Portable Programs = = ================================================================================ 6. MultiBoot USB-drives prepared with Make_USB.exe CD / DVD Content can be copied unchanged to Root of USB-stick by using the Add Extra Content Selector. This allows to use a well-tuned CD / DVD as Setup Source including Apps for Install of XP from USB. In this case you must Uncheck the Copy Checkbox of XP Setup Source Folder Selection so that this XP Source Selection is only used to have access to the XP BootFiles NTLDR and NTDETECT.COM and is NOT used as normal to Copy the XP Source to a Folder on Target Drive. Support for Ultimate Boot CD - UBCD ISO booting via boot.ini Menu from GRUB4DOS menu.lst Menu See Info of Icecube given in U_XP_SET\USB_XP_Setup\usb_cfg_extra folder. UBCD 5 - http://www.boot-land.net/forums/index.php?showtopic=7312 Support for LiveXP minint was added to the BartPE group of Make_USB.exe Autodetect of modified ntdetect.com when placed in U_XP_SET\USB_XP_Setup\makebt folder Support for VistaPE on MultiBoot USB-stick was made, where you can use the Vista Add Extra Source Selector to Select your VistaPE\Target\VistaPE-Core Folder. VistaPE - http://www.boot-land.net/forums/index.php?showforum=51 BOOT_IMG.exe can be used to Add Multiple BartPE type IMG or ISO files. LiveXP - BootSDI.img or BartPE.iso booting from RAMDISK must contain I386\SYSTEM32\DRIVERS\RAMDISK.SYS file of Windows 2003 SP1 In that case Win2k3 SP1 setupldr.bin is renamed as RMLD1 and patched for ramx1.sif file with the SetupData instead of winnt.sif The index in RMLDx can range from 1-9 for support of 9 different LiveXP Boot Image Files. http://www.911cd.net/forums//index.php?sho...21682&st=24 BOOT_IMG.exe can be used to Add Multiple CD-ISO Images as Boot Option to GRUB4DOS menu.lst Menu, where mapping of the ISO image to (hd32) or (0xff) is used. VistaPE and Windows PE 2.1 ISO are booting from RAMDISK this way. Other CD-ISO images when Installed on HD are copied first to RAM using the --mem option, so that Harddisk operations are allowed. In the case of Removable USB-stick the --mem option is NOT used in order to gain speed in all cases. Then the CD-ISO Files need to be contiguous (unfragmented), check and repair with wincontig: http://diddy.boot-land.net/grub4dos/files/map.htm Parted Magic 4.0 of Patrick Verner and Icecube is a handy Partition Manager. Parted Magic can be booted with grub4dos iso emulation. http://partedmagic.com/documentation/124-g...so-booting.html Download pmagic-grub4dos-4.0.iso.zip from http://www.digitalincursion.net/partedmagic/ Use latest BOOT_IMG.exe to Install pmagic-4.0.iso as GRUB4DOS Boot Option in menu.lst on your Harddisk or USB-stick. menu.lst title Boot pmagic-4.0.iso - ISO from RAMfind --set-root --ignore-floppies /pmagic-4.0.isomap --mem /pmagic-4.0.iso (0xff)map --hookroot (0xff)chainloader (0xff) After Booting with Parted Magic ISO from GRUB4DOS menu.lst on Harddisk, you can use GParted to change the partioning of your USB-stick e.g. to Create a second partition. In a similar way Booting from HD with LiveXP BootSDI.img into RAMDISK allows to use Acronis Disk Director 10 to create multiple partitions on USB-stick, without any need to use a filter driver as needed in regular Windows XP. Guides on How to Make MultiBoot USB Drives: Make_USB.exe is used to make MultiBoot USB-sticks having NTLDR-type bootsector and boot.ini Menu plus GRUB4DOS menu.lst Menu. NTLDR + NTDETECT.COM and boot.ini are copied to the root of an USB-stick previously NTFS formatted with Format Stick procedure, so that it is configured as a Harddisk having NTLDR-type BootSector. BOOTMGR-type Bootsector made by Vista Disk Management will be changed to the compatible NTLDR-type Bootsector. This is the way to make Bootable USB-stick with boot.ini Menu, where GRUB4DOS grldr can be launched from boot.ini Menu. Booting is as: MBR > BootSector > NTLDR > boot.ini > grldr > menu.lst The Bootsector refers to NTLDR file in Root of USB-stick or Harddisk Windows XP can be launched from any primary partition of any harddisk using arcpath in boot.ini Menu. Windows Vista can be launched from any harddisk using chainload of bootmgr in menu.lst Menu of GRUB4DOS. Make_USB.exe can also be used to Install LiveXP BootSDI.img as Boot option on e.g. 30 GB USB Harddisk Primary partition, previously Formatted with NTFS FileSystem using Windows XP or Vista Disk Management. Guide for MultiBoot USB-stick with boot.ini Menu http://www.911cd.net/forums//index.php?showtopic=20089 Important Info on making MultiBoot USB-drives was given by diddy in 2 Guides: Guide for Multi-booting from a USB Drive http://www.911cd.net/forums//index.php?showtopic=18846 Multiboot Usb (pe, Linux And Dos), Using Syslinux, GRUB4DOS and/or multiple partitions Grub4dos Guide http://diddy.boot-land.net/grub4dos/Grub4dos.htm More Info on Booting with GRUB4DOS grldr with menu.lst Menu http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial grub4dos, .iso images and (hd32) or (0xFF) mapping http://www.boot-land.net/forums/index.php?showtopic=5041 Install of Grub4dos MBR BootCode is used to make Bootable USB-sticks without the need of having XP Setup Source. Booting is as: MBR > grldr > menu.lst In this case Grub4dos grldr BootLoader can e.g. direct Boot CD ISO or DOS floppy images or chainload BOOTMGR of Vista or Windows 7 Setup Source. = = ================================================================================ Format Stick using Make_USB.exe An AutoIt3 Routine was created to Format USB-sticks with a Harddisk like structure and NTFS/FAT32/FAT FileSystem. It can be used in Make_USB.exe with the Format Stick Button instead of using the HP Format Tool. First 100 Sectors of USB-stick are erased quickly using dsfi.exe and file Erase_100.bin MBR BootCode is obtained from XP file dmadmin.exe just as in MBRBatch.cmd made by jaclaz http://www.boot-land.net/forums/?showtopic=3191 Partition Table entry is constructed from the USB-stick CHS geometry as derived from MBRWiz.exe /list Partition is ending on Cylinder boundary to improve bootability as compared to HP Format Tool, which would give a CHS-LBA unbalanced partition. CHS Knockout Patches and Dummy Second Partition are user selectable options to improve USB-stick bootability CHS Knockout Patches can be applied to XP-MBR BootCode (HP Patch) http://www.boot-land.net/forums/index.php?...=2246&st=15 and to FAT32 or NTFS BootSector to improve bootability as described by Clemens Fruhwirth and tested by cdob to be useful. http://blog.clemens.endorphin.org/2007/12/...ndows_3170.html http://www.911cd.net/forums//index.php?sho...1702&st=129 http://www.boot-land.net/forums/index.php?...5306&st=215 http://www.boot-land.net/forums/index.php?showtopic=8528 Apply HP Patch to USB-stick XP-MBR Code for CHS Knock-out Change at offset 0xCA 3 bytes - 0xB8 0x01 0x02 --> patched to 0xEB 0x1A 0x90 Apply 4x NOP Patch to FAT32 and NTFS BootSector for CHS Knock-out FAT32 boot sector ("MSDOS5.0" found at offset 0x03) : Change at offset 0xE6 - 4 bytes - 0x0F 0x82 0x4A 0x00 --> patched to 0x90 0x90 0x90 0x90 NTFS boot sector ("NTFS" found at offset 0x03) : Change at offset 0xD9 - 4 bytes - 0x0F 0x82 0x3A 0x00 --> patched to 0x90 0x90 0x90 0x90 USB-sticks with Dummy Second Partition of about 8 MB (using 1 Cyl in case of n/255/63 geometry) can be generated to further improve bootability as described by online http://www.boot-land.net/forums/index.php?showtopic=7512 The Format Stick routine was further improved for FAT and FAT32 FileSystem, by patching after Format two important bytes which determine bootability of USB-stick. MBR - Reset FAT FileSystem byte = 0E (LBA) at offset 0x1C2 in MBR, after format it was 06 (CHS) and not bootable FAT BootSector - drive-id patch 0x80 at offset 0x24 , after format it was 00 and Not bootable MBR - Reset FAT32 FileSystem byte = 0C (LBA) at offset 0x1C2 in MBR, after format it was 0B (CHS) and Not bootable FAT32 Bootsector - drive-id patch 0x80 at offset 0x40 , after format it was 00 and Not bootable FAT and FAT32 USB-stick are NOT bootable without patching these two critical bytes, and flashing cursor or Disk Error would be the result. The problem is that Windows OS all the time tries to reset these bytes to NON-bootable value. But this problem was overcome in the present procedure. ================================================================================ 7. Make_IMG.exe - Make and Install Boot Image File - Type IMG or ISO Supported are: Make and Install 15 MB FreeDOS FAT12 Superfloppy IMG file from Source Folder containing kernel.sys Make and Install 25 MB MS-DOS FAT16 Superfloppy IMG file from Source Folder containing IO.SYS Make and Install 15 MB XP Recovery Console FAT12 IMG file Booting from RAMDISK and made from Windows XP Setup Source Make and Install LiveXP / BartPE / UBCD4Win ISO or NTFS Compressed IMG Files Booting from RAMDISK (max 500 MB) Install WinPE 2.1 or VistaPE ISO files Booting from RAMDISK Install CD-ISO file e.g. ubcd50b12.iso or pmagic-4.0.iso or LiveXP_RAM.iso as boot option in GRUB4DOS menu.lst Menu Images are made from a Virtual Drive by using ImDisk virtual disk driver of Olof Lagerkvist http://www.ltr-data.se/opencode.html For using Make_IMG.exe it needs to install previously the ImDisk Driver with U_XP_SET\USB_XP_Setup\makebt\imdiskinst.exe You will find the Image files made with Make_IMG.exe in U_XP_SET\USB_XP_Setup\makebt\make_image folder. For the XP Recovery Console a 15 MB FAT12 Superfloppy Image file is made, where the cmdcons folder is generated by parsing dosnet.inf of the Windows XP Setup Source. Then cmdcons folder is renamed as i386 and ramdisk.sys of win2k3 is added instead of the original one. In root of bootdrive we have setupldr.bin of win2k3 renamed as the bootloader RCLDR, which is patched for using rcons.sif as setup information instead of winnt.sif to allow MultiBoot Environment. More Info: http://www.boot-land.net/forums/index.php?...=5316&st=60 I would like to thank jaclaz for making use of his CATCH22 folder. http://www.911cd.net/forums//index.php?sho...20983&st=25 Adding the CATCH22 folder to the root of any HD-like device allows to use Recovery Console Superfloppy Boot Image without using admin password and to get unlimited access to any folder by connecting to CATCH22 instead of to WINDOWS folder and then using the command: batch SETALLON For the LiveXP / BartPE / UBCD4Win ISO or NTFS Compressed IMG Files Booting from RAMDISK, it is possible to migrate USB-stick to DriveLetter U: so that Shifting of other Drive Letters is prevented. In root of boot drive we have Win2k3 SP1 setupldr.bin renamed as RMLD1 and patched for ramx1.sif file with the SetupData instead of winnt.sif The index in RMLDx can range from 1-9 for support of 9 different LiveXP Boot Image Files. http://www.911cd.net/forums//index.php?sho...21682&st=24 Install of Boot Image files is possble on Harddisk Boot Drive C: or on Bootable USB-stick made e.g. with Make_USB.exe by making boot entries in GRUB4DOS menu.lst Menu and in some cases in XP boot.ini Menu as well. The program will recognize the type of image and will generate the corresponding GRUB4DOS entry in menu.lst The DOS Superfloppy Images including DOS-Apps are booting from RAM, which allows to boot with DOS from a NTFS Harddisk. FreeDOS Superfloppy file BTFRDOS.img is in folder Downloads - http://wimb.winbuilder.net/downloads/ GRUB4DOS is updated to the latest version grub4dos-0.4.4-2009-06-11 which is also essential for booting the DOS Superfloppy Images using the generated menu.lst entries. More Info on GRUB4DOS Menu entries for various types of Image files: http://www.boot-land.net/forums/index.php?showtopic=5041 http://diddy.boot-land.net/grub4dos/Grub4dos.htm = = ================================================================================ Summary After preparing your USB-stick with Make_USB.exe we have two cases, each of them needs Booting from HD into RAMDISK with a compatible PE Boot Image. Install of XP needs Booting with LiveXP - IMG allowing to format Install Drive with NTLDR type BootSector. Install of Vista and Windows 7 need Booting with Windows PE 2 - ISO allowing to format Install Drive with BOOTMGR type BootSector. Procedure - Install XP from USB-stick Connect USB-stick and Run BOOT_IMG.exe Install LiveXP IMG in boot.ini / GRUB4DOS Menu on Harddisk HD Boot LiveXP into Ramdisk - Quick Format and Run USB_XP_Setup.exe HD Reboot and Select XP Setup from boot.ini Menu Keep USB-stick Connected Until AFTER Logon XP Procedure - Install Vista or Windows 7 from USB-stick Run BOOT_IMG.exe Install Windows PE 2 ISO in GRUB4DOS Menu on Harddisk HD Boot Windows PE 2 into Ramdisk - Start Vista Setup from USB Precisely on First Reboot - Remove USB-stick The present approach is Install from USB without booting from USB. So you don't need BIOS USB Boot Support and you don't need to change BIOS Settings. Moreover, Unchanged Setup Sources can be used and can be located in a folder on USB-stick so that they do not interfere with eachother. ================================================================================ LiveXP + U_XP_SET = = Credits: I would like to thank ilko_t for publishing his AutoIt3 Source of WinSetupFromUSB_0-1-1.au3 at MSFN Forum http://www.msfn.org/board/index.php?showtopic=120444 Parts of WinSetupFromUSB were used for Creating Make_USB.exe ================================================================================ From Tutorial at BootLand: http://www.boot-land.net/forums/?showtopic=5306 The original topic was started on July 29, 2008 and was closed at January 4, 2010 because it was often inaccessible due to overload (nr of pageviews was 132.698) ================================================================================
  4. Disclaimer: Use at own risk ! ---------------------------------------------------------------------------- What is it for: Fixing Errors, & most of the Eventlog Errors (from a fresh or older Win10) by Service Config ---------------------------------------------------------------------------- Why: - Errors in the Eventviewer after a fresh install - Some services was changed, you maybe didn't realize, but what you get, is that the Store, Windows Update & more couldn't run, properly anymore. - My Experience is, most problems that appear on "friends" computers in Windows 10, belongs to the Service config ! ---------------------------------------------------------------------------- Some weird Examples I've found: - get Eventlog Errors by change LanmanWorkstation from Auto to Demand (On Demand, it will be started anyway) - get Eventlog Errors by change WSearch (Indexing) from Auto to demand, but NOT if you set it to disabled... ??? ---------------------------------------------------------------------------- Fixes Errors & Eventlog errors like: - DNS Client (v10 Vortex+wpad) EventID 1014 - Service Control Manager (CldFlt+Spooler+iphlpsvc+Printer+Update Orchester) Event ID 7000 - DistributedCom (SID: Nicht verfügbar) ID1016 - SecurityCenter (SECURITY_PRODUCT_STATE_ON) EventID 16 - Perflib (Bits) EventID 1008 - Application Error (MRT.exe) EventID 1000 - DHCP CLient (DHCP Waiting) EventID 50160 - AppModel-Runtime (0x800700B7) EventID 37 - User Device Registration EventID 360 - Pipe Closed Errors - Windows Store Problems (0x80072ee7) - Cluster Errors & more ---------------------------------------------------------------------------- Limits: - English\German Windows only, cause MS translated the ALC Permission Names (the user BUILTIN\Administrators is called VORDEFINIERT\Administratoren on a German Windows oO) - Intention is to fix Errors, maybe you have reasons, to keep a service disabled, even if it provide errors - Can't and won't change following 4 Services: DcomLaunch, RpcSs, WinDefend, gpsvc - don't try !!! - Permissionchanges are permanent, sorry. - I would like to set them to their Original State after, but feels like to much work. BUILTIN\Administrators Allow FullControl (A;OICI;KA;;;BA) will be added on some Registry Service Entry's. - Doesn't change, or restore, driver states that can controlled with SC command, cause: one single error here, and Windows is smashed... - Doesn't fix KernelPnP (WudfRd) EventID 219 - This one can be fixed with "snappy driver installer" or similar which is using the driverpacks ---------------------------------------------------------------------------- Changes: 23.07.2017 - Add a Powershell policy bypass - Add OS Language Check exitloop (Script is for English and German only, and will exits on other Systems !) - Kept NcaSvc, WEPHOSTSVC and WiaRpc at Original State (cause one or all three, could be needed...) ---------------------------------------------------------------------------- Files: Download -> R4D3_Fixes.zip <- Download or here link https://www.file-upload.com/jd6our1a5hrg R4D3_Fix_All_Services_to_Default.bat - Change All Services to their Original State 1. OS Language will be checked 2. Services with Variable Names will be searched, and declared as variables (could take a while) 3. A Powershellscript runs with that Variables to get Full Adminrights on Permissionprotected Services From: www.alkanesolutions.co.uk/2016/06/29/set-registry-key-permissions-powershell 3. Some Services will be Changed via REG ADD (cause they can't be changed via SC) 4. NTFS-Registry Permission Protected Services will be changed to their Original State 5. Other Services will be changed to their Original State ---------------------------------------------------------------------------- R4D3_Fix_Service_Config.bat - Changes the following Servicestates Demand: CDPUserSvc_xxx = CDPUserSvc_xxx CDPSvc = Connected Devices Platform Service DoSvc = Delivery Optimization Service FontCache = FontCache MapsBroker = Downloaded Maps Manager NlaSvc = Network Location Awareness OneSyncSvc_xxx = OneSyncSvc Disabled: AxInstSV = ActiveX-Installer (needed sometimes in domain networks) CldFlt = Cloud Files Mini Filter Driver (no reason for that one) DiagTrack = Diagnostics Tracking Service (no thanks) DusmSvc = Data Usage (no thanks) iphlpsvc = IP Helper Service (keep, if you use IPv6) lfsvc = Geolocation Service (no thanks) MSiSCSI = Microsoft iSCSI Initiator Service (something for servers) RetailDemo = RetailDemo (no thanks) SCPolicySvc = Smart Card Removal Policy Service (never seen someone using a smartcard reader) SessionEnv = Remote Desktop Configuration (for remote desktops) SysMain = Superfetch (stop unnecessary writings on my ssd) TrkWks = Distributed Link Tracking Client (nobody need that) UmRdpService = Remote Desktop Services (for Terminal RDP Connections) W32Time = Windows Time service (to get rid off it ADMIN CMD: w32tm.exe /unregister) WbioSrvc = Windows Biometric Service (no thanks) WinHttpAutoProxySvc = WinHTTP Web Proxy Auto-Discovery Service (for Domain? Networks with Proxy Server) WMPNetworkSvc = Windows Media Player Network Sharing Service (for PlugAndPlay Network Media Devices ???) workfolderssvc = Microsoft Work Folders (needed sometimes in domain Networks) WSearch = Indexservice (stop unnecessary writings on my ssd/laptophdd) ---------------------------------------------------------------------------- R4D3_Fix_Homegroup_Assistent.bat (Fixes Error 0x80630203, where a homegroup could not be changed or joined) - It just deletes the protected crypto files in \Users\All Users\Microsoft\Crypto\RSA\MachineKeys ---------------------------------------------------------------------------- R4D3_Fix_Geolocation_Service.bat (Fixes the Error, that Geolocation Service could not be Started, via Removing a "false Trigger Info Reg Key") ---------------------------------------------------------------------------- R4D3_CleanUp_All_Event_Logs (cmd wmic Shortcut) ---------------------------------------------------------------------------- R4D3_Restart_Special (cmd shutdown Shortcut) ---------------------------------------------------------------------------- R4D3_Show_Activ_Connections (cmd netstat Shortcut) ---------------------------------------------------------------------------- R4D3_Reg_Tweaks.reg (some regtweaks, mostly for ssd, read the comments in the reg, before using) ---------------------------------------------------------------------------- Usage: 1) Important: You need to right click each file first, and click allow (there is a flag on the files: file is from another computer...) 2) (Optional) Cause I disable the indexservice, I would suggest to remove the indexes before (right click properties c: -> disable indexoption, then: in control panel under index, remove the folders, and rewrite the index... - both steps could be take a really long long time...) 3) .bat Files and Shortcuts needs to be run with ADMINRIGHTS to work properly (Mouse right click on the file and then ...) 4) (Optional) Cleanup your Eventlogs first - from a Console with Adminrights type: (or use the Shortcut) for /F "tokens=*" %1 in ('wevtutil.exe el') DO wevtutil.exe cl "%1" 5) Run "R4D3_Fix_All_Services_to_Default.bat" as Admin (Highly Recommend) 6) Run "R4D3_Fix_Service_Config.bat" as Admin (or edit it first to fit your needs) 7) Restart Your Computer (Optional: "Special Refresh [Cache???] Restart" via Adminconsole "C:\Windows\System32\cmd.exe /c "shutdown -g -t 0" (or use the Shortcut) 8) (Optional) Check your Logs in Eventviewer ! 9) (Optional) Test and Tell me, what Problem my Script fixed for you... Notes, you can: - Check all Service acl flags with powershell: Get-ACL "HKLM:\SYSTEM\CurrentControlSet\Services\*" |Format-List - Check Service Driver Dependencies: for /f "tokens=2" %s in ('sc query type^= driver ^| find "SERVICE_NAME"') do sc EnumDepend %s - Check Service States Config: for /f "tokens=2" %s in ('sc query state^= all ^| findstr "SERVICE_NAME"') do @(for /f "tokens=3" %t in ('sc qc %s ^| findstr "START_TYPE"') do @echo xxx %s = %t) Kept from Old Post: - would be awesome if someone could change the Snippet that the output is: xxx SERVICE_NAME = START_TYPE = DISPLAY_NAME
  5. Wondering if someone has some atlas updated/fixed for Creator Update. @NoelC , maybe? :3 Actually, some of the Atlas I had for Anniversary Update, still works in CU, but they "paint" the windows border, which is not present anymore in "vanilla" windows and show border even on start, which is quite ugly and pointless.
  6. Hey Folks, i got crazy last days, cause there was absolut no way, to connect my Bluetooth headphones in a Quality Stereo mode, on my Laptop... - doesnt matter which driver i chosed, it just didn´t work as expected… - i searched Google, and there are allready some tips out there, but they didn´t help… - cause i couldn´t choose the Stereo mode in Sound Options, and so on... 8000 Hz with mono only... Here you can see the problem: HOW TO FIX: DISABLE: Bluetooth Audio Gateway Service (BTAGService), than restart Info: If you need the mic, than this is no solution… - but i am glad, that i found a fix after spending 2 days installing drivers, etc... Maybe: you need to remove, and pair the bt device after Restart...
  7. As the title says, I was doing sysprep on my PC so I could transfer the hard drive to a new system. I let it run through the night, through the morning, and I checked the log. I noticed that only every thirty minutes does sysprep take an action. What can I do to remedy this?
  8. Hi all, I want to create bootable live Windows PE on usb stick. I want to create it from Windows 10 installation i have. I wonder, how can i achive that? Any instructions? Thanks, Rami
  9. Microsoft released in a TechNet blog post on February 1st that Office 2019 (Scheduled for release later in 2018) Will only be supported on Windows 10. They also reveal in the post that it will be supported for only 7 years (5 Mainstream, 2 Extended) Rather than the usual 10 years. Office 365 will suffer a similar fate in 2020 it would seem. Source: https://blogs.technet.microsoft.com/windowsitpro/2018/02/01/changes-to-office-and-windows-servicing-and-support/ EDIT: Albeit unsupported, It has been made to work on Windows 8.x. Not like anyone needs new versions of office, anyways...
  10. Yep, another program that helps to prevent Windows 10 from automatically update. this one comes from NoVirusThanks, a software developer that gave the world a few programs like Exe Radar Pro. that I've read a lot good about on security-related sites. Some might find it handy. http://www.novirusthanks.org/products/win-update-stop/ Personally I didn't test. It says it supports all 32/64 bit Windows from XP to 10, but I find Win7 built-in tools for that purpose quite better than the one in Win 10 Wilders Security thread (quite brief at the moment of posting).
  11. Hi everyone! I'm wondering if it's any Windows 10 Unattended Guide around here. I would be more than happy to participate in building it if it's not! Thank you!
  12. I have no words to describe the mess Microsoft created in the font rendering in Windows 10. Just look at this explorer window. Some elements like title bar and address bar have a grayscale antialiasing, the rest has cleartype enabled. Ok, let's open ClearType Tuner and select a third option on a third page which is a grayscale cleartype. And guess what, it's still the same! This tool has no effect at all on the cleartype's color settings. Disabling cleartype is no option, as the text becomes a total mess. So the question is: How can I force Windows to use that grayscale cleartype smoothing method on all of the GUI elements? If this is some kind of a new font used on the titlebars, can I use it on the other elements by editing aero.msstyle or shellstyle.dll? p.s. The reason of my post is that I use one display with RGB matrix and the other with BGR, So I have to constantly switch the cleartype's sub pixel matrix to get rid of blurred fonts.
  13. Here's the issue When going to Word 2010 starting an envelope, we click the Address Book icon to view addresses from Outlook. It is completely empty. If we check Outlook, it has all the addresses and works fine. We just can't see the address book in Word to do envelopes. Here's what we are using: Windows 10 Home 64bit (Brand new computer - 1 week old) Office Home and Business 2010 What we've tried with no success. We created a new Outlook profile. We created a new PST file and imported the address book into that new PST file. We tried with Outlook open and closed. Other software same as previous computer which worked fine. It never worked on this new computer. I hope someone has a suggestion that might work?
  14. If anyone uses Microsoft Windows Bob 10 , they might find this guide useful: Manage connections from Windows operating system components to Microsoft services It covers the official s*** that tries to phone home to provide "enhanced services" half of which you may have no use for.
  15. Is there a way to use an MUI'd Windows 10 install for an upgrade install of different languages? When I start the install from the root of the Multi-language media on a windows in a different language than the original I get a message that the upgrade isn't possible because the language is different. On Windows 7 this is not a problem. When I start setup.exe from the root of the media I get a chance to select the language and everything runs fine. On Windows 10 I have to start setup from the "sources" folder for the language selection screen to appear, but then when I select "Upgrade" setup tells me to start from the root of the media.
  16. Windows 8 and Windows 10 have a new "feature" called "Fast Startup", "Fast Boot", or "Hybrid Boot". This is a form of mini-Hibernate Mode. Unlike full Hibernate, this is not documented in the Shutdown User Interface and is enabled by default. If you Shutdown, not Restart, Windows 8 or 10, this Mode will save the File Cache in the Hibernation File. If you then modify any of these Cached Drives using a different OS Instance, then access it again from the original OS Instance, the Cache will not match what is on the Drive. If you then make changes, the Cache will be written to the Drive possibly corrupting it. Windows often writes to Drives in the background, so you can corrupt a Drive even if you do not intentionally write to it. There are numerous reports of this problem along with instructions on turning off Fast Startup on Google. I strongly recommend that anyone using Multi-Boot or swappable Drives, including Virtual ones, disable Fast Startup if using Windows 8 or 10. In a pinch, always select Restart, not Shutdown, when closing Windows 8 or 10 if Fast Startup has not been disabled. For those of you not born yesterday, never put a writable Floppy Disk into a Windows 10 system. It will be corrupted even if you don't intentionally write to it.
  17. After much of tests i was able to write a Powershell Script, that replace, all inherits of all folders and subfolders (even the one with long names), without taking the Ownership ! Reasons: - Taking the Ownership of a Windows Folder can make much Problems ! (I dont like solutions, that can make more problems than they solve, and i even dont like it, if people say, dont change Permissions of systemfolders blabla - Me, the Owner of my Harddrive, like to have R/W Permissions to all Folders, but some folders get there permission inherit from a Top Folder, and so, i wasnt able to set their permissions... so many commands iacls, dir -ad, some powershell commands and ways, just didn´t do it, but i was able to to it (R4 never gives up...) 1) You need to allow Powershellscripts - in a Powershell console (with Adminrights) run: Set-ExecutionPolicy RemoteSigned (maybe "unrestricted could do the job too, you can set it back to restricted later) 2) Then run the script (with Adminrights too) 3) THis could take a while !!! Some really rare folders (probably Symbolic NTFS Links, Junctions or Similar) give Errormessages, - you can ignore it ! cd "C:\" foreach ($i in Get-ChildItem -Recurse -Force| ?{ $_.PSIsContainer}) { echo $i.FullName $acl=Get-ACL $i.FullName $acl.SetAccessRuleProtection($True, $True) Set-Acl $i.FullName -AclObject $acl } (this little success brings me some steps forward, in getting a clean os, - next step is setting r/w permissions for buildIN Admin, and then check the 1355 dll´s i identified, that can be called by regsvr32) - (maybe i could replace reginherits too...) mfg R4D3 Edit: Uhm, sorry my Script seems to switch all folderinherits like 180 degree (good for folders with inherits, but not for folders without - SetAccessRuleProtection($True, $False) seems to be better, and with giving Adminrights this hopefully does it: Edit: Just moved $acl.SetAccessRuleProtection($True, $True) before the new rule (cause, first the existing inherits must be replaced with local one, before the new-Object Rule, took them off and give Built-In Admin permissions.... cd "C:\" foreach ($i in Get-ChildItem -Recurse -Force| ?{$_.PSIsContainer}){ echo $i.FullName $acl=Get-ACL $i.FullName $person=[System.Security.Principal.NTAccount]"BUILTIN\Administrators" $access=[System.Security.AccessControl.FileSystemRights]"FullControl" $inheritance=[System.Security.AccessControl.InheritanceFlags]"ObjectInherit" $propagation=[System.Security.AccessControl.PropagationFlags]"None" $type=[System.Security.AccessControl.AccessControlType]"Allow" $acl.SetAccessRuleProtection($True, $True) $rule=New-Object System.Security.AccessControl.FileSystemAccessRule($person,$access,$inheritance,$propagation,$type) $acl.AddAccessRule($rule) $acl.SetAccessRule($rule) Set-Acl $i.FullName -AclObject $acl }
  18. carlitosoo555

    What do you think of "Neon" so far?

    In my opinion it looks good, (not as well as AG) and is very well optimized, what do you think? Do you like this kind of "transparency" and "blur"?
  19. I just installed Aero Glass for Windows 10, and it has changed almost nothing. No taskbar transparency, no transparent borders, no rounded borders at the corners, no windows 7-style buttons. All it did was add color to the bar and buttons at the top of each windows. I did verify that I installed the correct version. Take a look. How do I get it to work? Also, that "Aero Glass for Win 8.1 / http://www.glass8.eu" text really annoys me. How do I remove it?
  20. Hi, First of all let's not be hypocrites and act like you've never pirated ANY softwares in your life. So please do NOT come to me like "oh my god you should buy Windows 10 instead of simply obtaining it from non legitimate sources." And at the end of the day it's the dev's fault for making it very easy to bypass things. So has any of you succeeded to do a fresh install with a pirated copy of Windows 10? I found no way to do that because it seems impossible to get a key that works. Any tips, please? Thanks!
  21. how do i remove the watermark? i got given a licence key but no idea where to put it. My download didnt have a donation.key or something like that. Its Aero Glass For Windows 10. Thanks also installed everything correctly
  22. Hi, hoping someone can help. I have a WinPE USB drive that I boot various devices from in order to deploy bespoke images (All Windows 10 Pro 64 Bit) .. I would like to have the bespoke image contained onto a 32GB MicroSD Card .. however, on all but 2 of the 5 different devices I want to do this for WinPE does not pick up the SD Card. ie running DISKPART - LIST DISK shows only the main HD and the USB, on one of the other devices I can force load the Realtek driver using DRVLOAD.EXE, I was hoping to do the same with the other devices .. but none of the others use the Realtek driver, they all use the standard Microsoft Driver and I have no idea what .INF file to use in conjunction with DRVLOAD in order to force load the driver and gain access to the SD Card.
  23. Dear all, I need unattend xml file for windows 10 anniversary update which must have capablity to join pc on domain, with computer name etc. i have one for windows 7 which is perfectly working with WDS 2012. But this is not working for windows 10 build 3607 Anniversary Update. Can anybody fix this for windows 10 or provide new one for windows 10 anniversary update. It is not joining on domain and not naming pc properly for windows 10. This file is for windows 7. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey> <ComputerName>*</ComputerName> <TimeZone>%TIMEZONE%</TimeZone> <RegisteredOrganization>atco</RegisteredOrganization> <RegisteredOwner>ATCOVDI</RegisteredOwner> </component> <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Identification> <Credentials> <Domain>mydomain.com</Domain> <Password>password</Password> <Username>username</Username> </Credentials> <JoinDomain>domain.com</JoinDomain> <MachineObjectOU>OU=Windows 7,OU=ThinClients,OU=ouname Desktops,OU=ouname,DC=domain,DC=com</MachineObjectOU> </Identification> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>en-us</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UILanguageFallback>en-us</UILanguageFallback> <UserLocale>en-us</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Password> <Value></Value> <PlainText>true</PlainText> </Password> <Enabled>true</Enabled> <Username>localthinuser</Username> </AutoLogon> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value></Value> <PlainText>true</PlainText> </Password> <Description>Local thin client user </Description> <DisplayName>localthinuser</DisplayName> <Group>Guests</Group> <Name>localthinuser</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <TimeZone>%TIMEZONE%</TimeZone> <RegisteredOrganization>Al Tamimi &amp; Co</RegisteredOrganization> <RegisteredOwner>ATCO</RegisteredOwner> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> </OOBE> </component> </settings> <cpi:offlineImage cpi:source="wim://servername/reminst/install.wim#Win7 Ent Basic (x64)" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
  24. I am using an Unattend.xml file to install Windows 10. My .cmd file requires internet access during the Specialize pass. Windows 8\10 contains the network driver for my ethernet adapter, so there is no problem there. On Windows 8.1, this is no problem. On Windows 10 TH2 (last third? version) this is no problem On Windows 10 TH2 (first version) - there is no internet connectivity (e.g. ping www.bbc.co.uk does not work) On Windows 10 Anniversary (first version) - there is no internet connectivity (e.g. ping does not work) - I did not test the second release of TH2. In other words, Microsoft fixed the bug in TH2 but the bug is now back in the Anniversary build! It seems that there is no host name set up in the 'bad' versions (e.g. ipconfig /all shows no host name). I can 'fix' the problem by running msoobe for 10 seconds and then killing the task - I then get a host name and ping works. Does anyone know a better way of getting internet connectivity to work during the Specialize phase?
  25. alacran

    Create OEM ISO

    You can download a 7/8.1/10 ISO from Microsoft using this tool: http://www.msfn.org/2016/09/25/microsoft-windows-office-iso-download-tool-4-00/ Later you can add all required files/folders to make that ISO or USB good for all OEM brands using the tool Project Only - No Query Tool [29.70 MB] from the links in this page: http://pasted.co/de1acca8 read text files inside the download, it is pretty clear. Source: https://forums.mydigitallife.info/threads/71555-Multi-OEM-Retail-Project-Continued NOTE: This is only good for OEM machines, this DO NOT activate the OS unless there is the required Slic or Serial in your Bios (from OEM manufacturer), so make sure you download the proper OS, for your machine, you can download Query Tool Only [109.82 KB] in advance to check wich OS is good for your equipment. Some AV claim this one is malware but IT IS NOT, false positive. alacran