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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2 Neutral

About NeoBeum

  • Birthday 01/01/1869

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just a heads up - ADK 18362.1 will break when applying 18362.113 LCU KB4497936 and SSU KB4500109 to 18362.30 Winre.wim. (Output Log at the End of this Post) https://support.microsoft.com/en-us/help/4500109/windows-10-update-kb4500109 https://support.microsoft.com/en-au/help/4497936/windows-10-update-kb4497936 Anyhow, some of you may already know, but some may not. The following Command is now possible: Get-AppxProvisionedPackage -Path $MountedImagePath | Remove-AppxProvisionedPackage The result is the following: Running that command for DISM was not possible for builds earlier than Windows 1809 as some packages were unable to be removed. 1903 allows complete removal of all packages. How it should be. Package List Microsoft.BingWeather_4.28.10351.0_neutral_~_8wekyb3d8bbwe Microsoft.DesktopAppInstaller_2019.314.2138.0_neutral_~_8wekyb3d8bbwe Microsoft.GetHelp_10.1706.20381.0_neutral_~_8wekyb3d8bbwe Microsoft.Getstarted_7.3.20251.0_neutral_~_8wekyb3d8bbwe Microsoft.HEIFImageExtension_1.0.13472.0_x64__8wekyb3d8bbwe Microsoft.Messaging_2019.125.32.0_neutral_~_8wekyb3d8bbwe Microsoft.Microsoft3DViewer_6.1903.4012.0_neutral_~_8wekyb3d8bbwe Microsoft.MicrosoftOfficeHub_18.1903.1152.0_neutral_~_8wekyb3d8bbwe Microsoft.MicrosoftSolitaireCollection_4.3.4032.0_neutral_~_8wekyb3d8bbwe Microsoft.MicrosoftStickyNotes_3.1.55.0_neutral_~_8wekyb3d8bbwe Microsoft.MixedReality.Portal_2000.19011.1132.0_neutral_~_8wekyb3d8bbwe Microsoft.MSPaint_2019.408.1721.0_neutral_~_8wekyb3d8bbwe Microsoft.Office.OneNote_16001.11601.20066.0_neutral_~_8wekyb3d8bbwe Microsoft.OneConnect_5.1902.361.0_neutral_~_8wekyb3d8bbwe Microsoft.People_2019.305.632.0_neutral_~_8wekyb3d8bbwe Microsoft.Print3D_3.3.311.0_neutral_~_8wekyb3d8bbwe Microsoft.ScreenSketch_2019.222.408.0_neutral_~_8wekyb3d8bbwe Microsoft.SkypeApp_14.42.60.0_neutral_~_kzf8qxf38zg5c Microsoft.StorePurchaseApp_11811.1001.1813.0_neutral_~_8wekyb3d8bbwe Microsoft.VP9VideoExtensions_1.0.20593.0_x64__8wekyb3d8bbwe Microsoft.Wallet_2.4.18324.0_neutral_~_8wekyb3d8bbwe Microsoft.WebMediaExtensions_1.0.13321.0_neutral_~_8wekyb3d8bbwe Microsoft.WebpImageExtension_1.0.12821.0_x64__8wekyb3d8bbwe Microsoft.Windows.Photos_2019.19021.18010.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsAlarms_2019.305.627.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsCalculator_10.1902.42.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsCamera_2019.124.60.0_neutral_~_8wekyb3d8bbwe microsoft.windowscommunicationsapps_16005.11425.20190.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsFeedbackHub_2019.327.1732.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsMaps_2019.325.2243.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsSoundRecorder_2019.305.610.0_neutral_~_8wekyb3d8bbwe Microsoft.WindowsStore_11811.1001.2713.0_neutral_~_8wekyb3d8bbwe Microsoft.Xbox.TCUI_1.24.10001.0_neutral_~_8wekyb3d8bbwe Microsoft.XboxApp_48.48.7001.0_neutral_~_8wekyb3d8bbwe Microsoft.XboxGameOverlay_1.40.16004.0_neutral_~_8wekyb3d8bbwe Microsoft.XboxGamingOverlay_2.26.28001.0_neutral_~_8wekyb3d8bbwe Microsoft.XboxIdentityProvider_12.50.6001.0_neutral_~_8wekyb3d8bbwe Microsoft.XboxSpeechToTextOverlay_1.21.13002.0_neutral_~_8wekyb3d8bbwe Microsoft.YourPhone_2019.411.120.0_neutral_~_8wekyb3d8bbwe Microsoft.ZuneMusic_2019.19031.11411.0_neutral_~_8wekyb3d8bbwe Microsoft.ZuneVideo_2019.19031.11411.0_neutral_~_8wekyb3d8bbwe ADK 18362.1, KB4497936, KB4500109 PS E:\WinROG> DISM /Mount-Image /ImageFile:winre.wim /Index:1 /MountDir:mount\RE Deployment Image Servicing and Management tool Version: 10.0.18362.1 Mounting image [==========================100.0%==========================] The operation completed successfully. PS E:\WinROG> DISM /Image:mount\RE /Add-Package /PackagePath:"\\Nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4500109-x64_b727d70aacc30ac3522c02b285164d908e818ad6.msu" Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package \\Nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4500109-x64_b727d70aacc30ac3522c02b285164d908e818ad6.msu [==========================100.0%==========================] The operation completed successfully. PS E:\WinROG> DISM /Image:E:\WinROG\mount\RE /Add-Package /PackagePath:"E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu" Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu [==========================100.0%==========================] E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80070002 Error: 2 The system cannot find the file specified. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log PS E:\WinROG> DISM /Image:E:\WinROG\mount\RE /Add-Package /PackagePath:"E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu" Deployment Image Servicing and Management tool Version: 10.0.18362.1 Error: 50 DISM does not support servicing a Windows Vista RTM or earlier operating system. If the operating system is supported check that SSShim.DLL is present. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
  2. 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? TL;DR: 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 )... 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.
  3. I have one... WMIC reporting that my Samsung 850 Pro is using IDE on my laptop
  4. Just wanted to say hello, and appologize to anyone in advance ... I stumbled on to this place when I found this So I just wanted to let everyone know just to ignore me because I'm an obnoxious turd that's just going swearing alot, and mostly at Microsoft and the people who work there... I don't even work in IT, but gee whiz, there's some dipsticks there. While we're at it, why don't we just all move to cloud based stuff... because the internet is awesome fast in Australia, Microsoft thought it would be a good idea to share wifi passwords with neighbours while we put a shrimp on the barbie. EDIT: Disclaimer: Forgot to say, If you suffer from mild epilepsy, don't look at my profile page. You've been warned.
  5. well I look forward with T-wrecking MS Windows 10 with this community
  6. Even though it's almost a decade late reply, and there's a possibility of extinction, I registered to post just to say: Holy s***, I thought I was the only one. I've been dropping FBombs in the Technet, MSDN but mostly the Windows forums because the place is filled with fudge packers. Keeping it simple... yes, you could do more with the powershell object eventually, but just a query and ... zzzzz All I wanted to do was query my Disk BusType/Connection/Interface, but apparently MSFT_Disk doesn't relay the correct information as it gets passed along the convoluted script chain in Windows 10. My slave Samsung 850 Pro was using IDE at one stage too apparently... I'll just go to my junk and brush the dust and rust off my 486
  • Create New...