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. 

Sign in to follow this  

Win10 Answer File - Parse Library & Diskpart inadequacy

Recommended Posts

If I start to modify the libraries used for installation, will Windows fail setup? Is there some sort of integrity check like in Android Build Environments?

MS are dipsticks.
WMIC reported Samsung SSD using IDE interface.
0 trust level. 
MSFT_Disk has member MSFT_Disk.BusType
MSFT_Disk has no member type for Interface.
Follow Class Inheritance.
class MSFT_Disk : MSFT_StorageObject, MSFT_StorageObject ---> Storagewmi.mof ----> MOF: Managed Object Format, ROOT\Microsoft\Windows\Storage\providers_v2 ----> WMI
Just want to query connected devices - no need for DISKPART elevation - ***** scripters = scrappy DISKPART = broken disks

Must Locate disk for Unattended Install. 
Windows Updates/Upgrades/Connection to interwebs breaks things
Use WMIC and FSUTIL for noobsafe query

Follow MS Partition recommendation.
Need Answer File. 
Can't shrink disk.
MS recommend s*** layout. 
Trust level -999
MS stupid.

So, is WMI part of the .NET Framework? (Read Rant Below) Jeepers, I'm only a student, but already I can see why every single time my disks get rearranged...

I'm either contemplating shredding the Answer File Parsing Library - to include a data type for Shrink Partition. I have NFI why MS haven't added this already.

Microsoft recommending GPT/UEFI Partition as [ESP][MSR][OS][RECOVERY] is BS, because the Default Windows 10 install will always put the 'Recovery Tools' ahead of the [ESP] and at 450MB, has another partition added 2 updates later due to size deficiency. None of their answer files have any solution - other than to run a script for DISKPART.

What's the best approach? Write a CMD.EXE wrapper in C++ to take control of the Preinstallation Environment? or hack at the Answer File Parsing lib where ever that is... ?

Then - if you add PowerShell to the equation - it just compounds the problems as there were some function cmdlets missing the last I was using PS, so I just said F.it and I'll use the CMD prompt from startnet.cmd. But that's when I realised there were other issues like receiving correct information - so having almost no trust in MS to do the job right, I was more inclined to just write a C++ console project to handle the PE and setup.

I was trying to discect the System drive and find out exactly where gets called and when, and that's when I stumbled across this... sitting in the System32\wmeb directory ... I got taught not to have SPACES IN FILE NAMES, let alone dynamic link libraries... it's like the guy that was meant to do this job had to take a p*** and said screw it, we'll just leave them there, IDGAF.


EDIT: Just reading the dates on those files... the ones awesomely named with (1), they must have been 1607 files that were superseded by the 1703 install... nfi why not merge files properly - or just remove duplicate rendundant files completely.

As a student, I think that's just f***kn lazy, and I want to punch that person in the face. It's an Installation or Setup for the OS... am I crazy for wanting to get that job done right, and done right the first time?



Customary Vent, as per Signature:

I was going to post something on the MSDN or Technet sites, but the first post I had where I complained about MSFT_Disk and the twits in charge of creating the get functions for cmdlets and cmd.exe functions are all over the shop when it comes to querying the Disk BusType. I also whinged about how retarded it (was, now 1709) that back in 1511-1703, if you actually decided to forkout money and upgrade your laptop/pc's Windows Edition from the dismal Candy Crushing POS Home Edition, to the Professional (Business Focused) Edition, which lo and behold was also riddled with Candy Crushing stupidity, you could do so without a DVD/Disc, and only needed a key. Too bad so sad if you had a OEM Home Edition, right? and then wanted to carry over your Professional to another PC because the last update fried the controller on your SSD because of Chipset and Driver mismatch - which you specifically set in GPEDIT.msc to not download anything... oh but wait... it's 1603 update... and GPEDIT entries were moved to the Enterprise SKU, and we'll just trollop some consumers by making a new edition called... "PROFESSIONAL EDUCATION" WOOOOOOOOOOOOOOO. But hey - it's all good, because the Retail Pro, wiped your HDD, which contained your OEM Installation - but it's all good, because you did back up the system drive for this wishywashy joke of an Upgrade, but wait... the System Image gets upgraded during it as well... GG. Long story short, I've been sending MS abuse about releasing a single disc with all editions, because it's literally packages that are just turned off ffs. I've gotten side tracked now - but basically the MSDN Forum Moderator told me that my query wasn't related to ... something about 'base classes' (MSFT_DISK )...


Hi NeoBeum,

According to your question is more related to Windows, you could post a new thread in following link. You could ask here according to the version of your windows.


The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions. 

the bulk of my post there was complaining about why my PCIE NVMe was so hard to enumerate and account for - because back in 2015, I preloaded Samsung's secnvme.inf into the Setup, which Windows wiped each major Update, and because Windows Setup uses Disk 0 as default, if not properly configured, the PCIE NVME device is enumerated after the SATA drives... I then gave another example where WMIC actually reported that my 2nd Samsung 850 Pro was using IDE.... so my level of trust is at 0, so I'm on a mission to fix their s*** for them, because it's been 3 years now, and the dropkicks still cant get it done right.

Edited by NeoBeum

Share this post

Link to post
Share on other sites

It is beyond normal Setup automation. If you need to use the shrink option for Diskpart, it is better to use Diskpart, DISM and BCDBoot to deploy rather than Setup.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...