Windows 10 Enterprise - Mother of all tweak scripts
Windows 10 Enterprise - Mother of all tweak scripts
ImDisk - How to compile
imdisk how to compile
WinRamTech for PE
Hi Guys,
Just wondering if any of you created maybe a script based on the "Enterprise" Version
http://winramtech.atwebpages.com/RAMDriv/ramdriv.htm
Didn't found it so far.
thx for Infos
Steel
Convert Windows 7 VM To Real Install: Possible?
I would like to install 7 Enterprise x64 in a VMware VM. This will be a clean install on UEFI/GPT. My goal is to create a clean, prepped baseline image that I can restore on my physical machine, instead of having to do clean installs of Windows every time I screw something up. I will be installing all Windows updates (but no drivers yet, or even VMware Tools, while it's in the VM). Afterwards I'll be doing some general tweaks/optimation. I will also be editing thousands of Registry entries and moving critical system folders (Program Files, Program Files (x86), ProgramData, and parts of the Users folder) to other partitions in the VM. This will also be accomplished via NTFS junctions. It would be a total bitch to have to do all these things on a clean install. I've tested my methods in a VM before, they work very well, and so I would like to migrate it outside of a VM.
I'll also need to defrag my images and make them (the disk image files) contiguous. I'll also be running Disk Cleanup, SFC /scannow to make sure no system files are corrupt, and checking each of VM's partitions for filesystem errors.
Once this is finished I would like to image the VM's 3 partitions (without the EFI partition) into discrete images which can be restored via imaging software to real partitions on real UEFI/GPT disks (no longer in a VM).
But my main concerns are:
1. What type of disk image should I use for the VM (vhd, vhdx, vdi, etc)?
2. Will the Windows install boot on real hardware once migrated outside a VM (assuming I create the boot files correctly)?
3. My target hardware will be an SSD with 16GB RAM, i7 CPU, and Nvidia/Intel graphics cards. But will Windows still "believe" it is in a VM once migrated? In other words, will it reacclimatize itself to the new hardware it's on, and perform like Windows on SSD should?
4. Will I need to "sysprep" the physical install after it is moved, or can this be skipped (I have zero experience with this)? I have read that this may be necessary to "generalize" the OS to prepare it for new hardware. This may also help me avoid the issue listed below, but not sure.
5. The VM disk image will be running in SCSI mode (I think, need to check again). But my physical target disk is SATA with AHCI activated. I know that an installed Windows will BSOD if the disk operation mode is changed out from under it. How can this be avoided/fixed? This, I think, is perhaps the biggest snag I'll hit.
6. How should I go about imaging the partitions? Does the VM's disk need to be online (booted and running) or offline during the imaging? Does the image need to be "mounted" before imaging (since it's RAW)? Should I image to external HDD, into another RAW image/disk image? And what software should be used (I'm thinking CloneZilla for best reliability and integrity)?
After migration is complete I will install drivers and make a finalized image of the necessary partitions.
Is there anything else I should take into consideration?
Thanks for any advice!
Edit: Before anyone asks why I'm seemingly nuts enough to move system folders, it's because I would like to keep the size of the C drive on SSD to a minimum, and keep writes on the SSD to a minimum. The folders will be located on 2 volumes on my HDD data drive. Any softwares that are desired to benefit from the SSD's speed will be installed to C:\Apps. And my main user profile folder will also remain on SSD. User and Windows Temp folders will be moved, as well as C:\Windows\Installer (where many programs store their installers/uninstallers), and C:\Windows\SoftwareDistribution (Windows Updates download folder). Hibernation (hiberfil.sys) will be disabled and the page file will be relocated to HDD. Afterwards all Windows-related partitions will be encrypted and reimaged once more.
how do i fix error: Selected path doesn't contain spaces and is invalid?
Help with Embedded System/PE/RamDisk/PCILock removal
I believe I am faced with a unique obstacle that most people would not encounter. I will try to keep the story short and concise as to get to the point but i think a little back story is required in order to help identify my goals.
Through work we purchase a branded laptop that is paid for from our salary over the course of time, once the device is paid for, they remove windows and it is now your laptop and you are required to purchase another one via the same method. I believe my device to be compromised either due to the above or a very persistent rootkit. I have little knowledge in how the boot process works but over the course of a year trying to remove this I have come familiar with some terms and practices.
I believe the item to be a hyper visor (ESXi, citrix, xen or otherwise), loading through PXE/Ramdisk/VHD/WIM/PE/CE or some other method during boot. Whatever it is has loaded it has also loaded on to all of my personal PC's and to me, is not removable. I imagine someone with good knowledge on the configuration of these items would find it much simpler to remove.
I have attempted zeroing the drive/completely different drive while resetting NVRAM, reformatting, rebuilding BCD store, windows of every version, linux in an attempt to core boot (which I am unable to load to my bootmgr as it is blocked), editing CLI namespaces, editing the WIM file, remounting it and reloading yet all have failed. All of the standard practices of dumping the BIOS/editing any type of boot configuration fail as I am sure it is most likely encrypted. I can successfully flash the BIOS and alter settings, although if they interfere with the boot process (IE: disable visualization via BIOS) they settings are reverted or it simply fails to load.
I won't ramble on explaining why I believe all these to be true as it may steer away help/considerations that I have not taken in to account, but I welcome any questions that may help me figure out what is on my computers and how to remove it. I think if I can identify what means were used to load the image it may be easier to establish how to remove these items.
Please see below for bcdedit /enum all information. Any advice on how to help me reclaim my privacy would be greatly appreciated. (I did just update to windows 10 and can revert back to any recommended version of windows if required) This information is from a Dell laptop (L502X) which is running UEFI mode with legacy support disabled and is not formatted as a GPT Disk. Currenly has 4 visible partitions: 100MB system/500MB recovery, 400GB C: and a 300GB backup partition.
sony xmb Intervideo Instanton linux
Hi guys
i'm trying to boot my intervideo instant on linux with grub4dos on my pc but it fails to start and leaving a message
"couldn't find valid ram disk image starting at 0"
"kernel panic - not syncing : VFS: Unable to mount root fs on unknown-block(1,0)
Can anybody help me
i've two files which contains the boot codes which is initrd.pam, kernel.pam
these 2 files contains
kernel.pam - /InstantON/ivi root=/dev/ram0 ramdisk=5120 vga=0x317
initrd.pam - /InstantON/ivi-fs
Saving errors with ImDisk 2.0.1 final
Hi,
bad surprise before close the system this night using the new 2.0.1.
From command line and context menu on a drive an choosing to save:
From the control panel save button:
The only way to be able to save it is with the context menu option "Unmount ImDisk virtual Disk" and with the control panel "Remove" button.
In other words:
- the options that prompt you to save to a file, works.
- directly save by command line, save button or save menu, don't.
Tested in Windows 2000 and Windows XP.
Sorry for not joining the beta testing so we could find this before the final version
Drive X: size
Hi. I build wim file but i can change size drive X: ? No from WinBuilder, but where is config file or registry for change item disk size?
Win7PE SE and Python
I'm trying to create an Win7PE SE image using WinBuilder 082..
I was able to create an working image but i need to find a way to add python to the image.I t
I tried to add WinPython (python portable) to Additional Files but the program stucks and becomes NOT RESPONSING for like an hour (and then i killed it).
What is the best way to add Python to a Win7PE image?
Thanks
Software overhaul?
Quick suggestion. I don't k now if you pay Microsoft (or whomever) for the fat file system licensing, but I have a suggestion. To avoid necessitating that, or stop the need to split iso's. I propose using the Linux file system ext4. There are freely available drivers for windows and OS X out there (which could be provided on your site).
Or maybe, the ISO manager could be the ext4 file system viewer AND firmware updater AND automatically do what's currently a custom job of having to create a config/isosel.bin and config/iso_filename.txt etc.
I'm also, essentially, willing to donate my time to writing the software required to make this as simple as possible.
total noob
Can I use LiveXP to build a [arghh ... true/ordinary/usual/regular] XP system on a USB, to which I can install new programs while the system is running from USB?
Just dreaming out loud, but my ideal system USB would ...
install fast linux-like drivers (esp for video!)
for some reason slow clunky low-res video just seems too "dos" for me
if video and system response is clunky I'd rather rip open the box, and stick in a dedicated "Sata-for-PE" disk and boot from it
basic hardware testing tools ...
EaseUS PM 9 ...
Ghisler's TC, with 7z, WinRar, other utils ...
NotePad++ ...
Summatra/Foxit ...
XnView/Irfanview ...
and lastly and probably a hard one for backup/restore
Terabyte U
somehow, linux has figured out how to build drivers for a fast response workspace -- I tried WinPE and BartPE a few years ago, but the video was ... just too low res, clunky and slow ... the setup flies were tricky
Thanks
Windows 10 Pro (July 29 official upgrade) - XBOOT shutdowns itself with Error
How to solve fast?
Windows 10 Pro official update July 29 from Windows 7 Ultra.
Error is following:
ERROR REPORT ( 08/03/2015 14:56:46 )
Please submit this error report to developer.
Operating System version :Microsoft Windows NT 6.2.9200.0
.NET Framework version :4.0.30319.42000
Error Message :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace :
at A.V.D()
at A.V.D(ImageItemBase , ProcessLog )
at A.KB.D()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
"Autochk program not found" when installing Windows 7
I got this error 3 times last night when trying to finish 7 install. My ISO is Microsoft-issued, verified with MSDN hashes. It works fine in VMware Workstation and VirtualBox. I did check and the autochk exe is found in C:\Windows (can't remember which subfolder, if any).
I tried installing from burned disc, USB, as well as from a NTFS partition with setup files stored there (using a FAT32 USB to bootstrap into UEFI mode). I also tried mounting the ISO in my Zalman VE 400. UEFI DUET was used, which I suspect isn't the issue.
I also tried creating all my partitions on both of my drives in advance, with the first SSD target disk containing only a FAT32 EFI volume and a 2nd NTFS volume for 7.
I tried both installing from imagex and bcdboot, as well as from the official GUI setup, after deleting all partitions and the partition tables from both disks. When using the GUI, setup reaches the end just before reboot, and says that the install couldn't be completed.
Strangely enough, I got this exact same error when restoring from official Alienware recovery discs, which will only restore in BIOS/MBR mode.
This thread is basically a continuation of my previous "Windows installation repeatedly fails to complete", but because I now have a very specific error and can't determine the cause, I started this topic. I no longer suspect my RAM to be the issue, or my drives, both of whose SMART data checks out fine, and both drives being relatively new (bought in the past 120 days).
I also noticed that no pagefile.sys or hiberfil.sys is ever created during install, by either the GUI or when using ImageX.
format option sanity checks missing?
what just happened to me:
Chainloading bootmgr by G4D on GPT style USB Stick fails
I created a BIOS bootable USB Stick (harddisk style) with 3 GPT-Partitions. Primary bootmanager is GRLDR (GRUB4DOS 0.4.6a 2012-12-05), renamed as "bootmgr". It boots fine on GPT and shows all partitions. When I tried to chainload the original Win7 bootmgr (renamed as "w7mgr") to boot my WIN7 OS on built-in harddisk I got "0x0000000e" error (=The boot selection failed because a required device is inaccessible). Of course I had adapted a local /BOOT/BCD on the USB Stick with "bcdedit" (and "EasyBCD" in a 2nd attempt). I loaded the local BCD hive for inspection to the registry and found out, that the appropriate element contains no drive/partition information of the local drive ( = inaccessible device ?). Does it need it at all ? Is renamed bootmgr the problem ?
Is it possible - by any means- to direct "w7mgr" (read as "bootmgr") to the local USB Stick so that it finds the BCD entry which points to "winload.exe" on my harddisk ?
Proposal/Request for FeedBack: Naming/Formatting of OS-ShortNames - Asking for Additions
Hi, i just wish to gain some feedback on the following topic
: Naming/Formatting of OS-ShortNames - Asking for Additions
I am using ( for nearly two decades right now ) a self-thought/-taught formatting of shortnames for Operating-systems in their diversifications, like editions, service-pack states, etc.
Let me explain on a basic version ( 1st Mutator|Phase || General Definition )
EXAM | For example :
BMWN61SC // BootMgr - MicroSoft - Windows - NT - Family: 6 - Generation: 1 - Family-Type|Family-Release: Server - Family-Edition|Family-Variant : Core
so Syntax in short is like
: BootLoader - OS:Manufacturer|Author|Class - OS:Name-General - OS:Family-Name - OS:Family-Version||-Title - OS:Family-Generation - OS:Family-Type||:Family-Release(Service-Pack|RollOut|Mutation) - OS:Edition||:Variant
some more examples to make it easier to understand
:
EXAM
:NMWN513H
Boot-Loader: NTLDR | Manufacturer: MicroSoft | OS-Name: Windows | OS-Family-Name: NT | OS-Family-Version: 5 | Family-Generation: 1 | Family-Release: 3 | Family-Edition: Home
... in clear-text as originally named : MicroSoft Windows XP SP3 Home Edition
:GCLDUP5A
Boot-Loader: GRUB | Manufacturer: Canonical | OS-Name: Linux | OS-Family-Name: Debian | OS-Family-Title: Ubuntu | Family-Generation: P=Precise-Pangolin=12.04 | Family-Release: 5 | Family-Edition: Alternate
... in clear-text as originally named : ( Debian-based Linux by Canonical ) Ubuntu Precise Pangolin 12.04 Release 5 Alternate
So you might have an idea, what my naming convention points out ; But what is it for ?
Due to the fact i am active with/on Computers of any kind since 1987 ( age of 10 ) and i am in need of systematics to remember things ( Asperger-Syndrome ) i use Schemes like these in any occasion to remember and define things ; You can think of it as a possibility to recognize things while itself points out in what context it is/will be used ;
I am using this naming-scheme ( vaguely remembering ) since the days of Suse-Linux 4 / Windows 98/, something inbetween; I got that idea while experiencing QNX in its Floppy-Based-Version and first contacts with the interna of Windows NT 3.1/4.0 and as i have always (coming from a HC-Background : Commodore C4/64 / Amiga 500 / Atari ST , etc. ) try to use things that are handled in the same manner indepent of analogue/digital || print/screen || handwritten/mnemonic to define what i am actually working on / running / using ;
So far to the story behind :
What i am out for ?
I wish to have some feedback on how you ( yes, each of you ) would handle OS-Short-Names according to my scheme; it's like having a counter-check on the variants i already use.
The reason why ?
Well, i am looking out for releasing my ' personal secrets ' in handling any kind of install/setup/deployment--tasks i've used in the last 3 decades and though i have always been able to differ things for myself, i was constantly asked what the cryptography secret behind this naming scheme is ; So i wish to have your thoughts to work it out as a precise scheme, in order to give it back to the community .
If you ask why One is using such a scheme :
Since the Home-Computer days ( besides custom disk-geometries / self-defined disk-access/-format ) we have a small but efficient and allday-used least common denominator for file/folder-naming/-sort :
It is mostly called FAT ( File Allocation Table )
and as ( especially here o reboot.pro ) most people know : FAT has some simple limitations, like
8.3-File-Names ( 8 chars followed by file-type-extension of 3 chars separated by dot ) ;
if you have counted the chars for my OS-Short-Naming you come to ?
BMWN513H || GCLDUP5A ... Yep, 8 characters
This kind of Naming can even be used on an Atari ST or a Commodore 64 .
However, i think i explained enough and in full detail.
It would be very nice and kind of all of you if you would please the request by just thinking out loud:
HOW WOULD YOU NAME THE OPERATING-SYSTEMS YOU PERSONALLY USE ACCORDING TO MY NAMING-CONVENTION GIVEN ABOVE ?
THANKS FOR YOUR INTEREST .
S466531257 BOSS
PAETH CLAUDIUSRAPHAEL
P.s.
: To the networking Guys and those that wish to state this is nonsense -- consider to remember the naming-limitations of NetBios / SMB/ Samba calls ( WorkGroups/Node-Names) ; you might see why it is useful to have a short-naming convention that is identical from file-based ( e.g.: for systems booted on uefi-systems ESP via grub4dos/plop from usb/pxe stored on FAT reachable as same-named-node in a network, possibly for experimental/teaching/learning-use in a home-/school- -network or in deployment-scenarios whereas you steer the deployment via wifi to xxx-nodes by stacking up the needed variants locally to them cisco-switches via serial // if you know about - you'll get the idea ... )
original embedded version made for x64?
which embedded version was the first available for x64 system?
I notice there is vista embedded and also embedded standard 2009 but I do not know how to determine which was first or if there was another version prior to these?
I want to study the Enhanced Write FIlter of the earliest versions to see if it is possible to incorporate into XPx64/server2003.
I think that the earliest version would probably be best for this but I could be incorrect about that.
thanks
Startup error (v 2.0.3) "temporary drive letter points to another device"
I've a trouble with new version 2.0.3, at system startup a virtual drive is created but isn't possible to format it (i.e. NTFS).
Error code: "temporary drive letter points to another device"
startup command (with admin privileges, at user logon):
imdisk -a -s 768M -m Z: -p "/v:RAMDisc /fs:ntfs /q /y"
... work perfectly with previous stable 1.9.4, "Z:" drive is correctly mounted in NTFS format.
O.S. Windows 7 Pro SP1 x64