well, it works wonders.
oh, one thing, if I may, before I forget, svbus paradoxically installs and registers with more difficulty than firadisk, especially in win11.
Posted 18 January 2022 - 12:42 AM
well, it works wonders.
oh, one thing, if I may, before I forget, svbus paradoxically installs and registers with more difficulty than firadisk, especially in win11.
Posted 18 January 2022 - 10:14 PM
well, it works wonders.
oh, one thing, if I may, before I forget, svbus paradoxically installs and registers with more difficulty than firadisk, especially in win11.
This is again another of your comments that are good for nothing, and only create confusion to readers.
firadisk DOES NOT work fine with grub4dos for MBR and Win10 or Win11.
firadisk DOES NOT work with grub4dos for UEFI.
Then why talk about firadisk? If the recommended driver is SVBus driver, that works fine from 7 to 11 in MBR and UEFI environments.
alacran
Posted 19 January 2022 - 04:35 AM
yes, provided it installed correctly, though. I did accept the recommentations as long as it did, and could not when it did not.
Posted 19 January 2022 - 05:28 AM
yes, provided it installed correctly, though. I did accept the recommentations as long as it did, and could not when it did not.
Fantastic, congratulations, you are really improving your non sence expresions, last sentence is so clear as:
Yes, you are not in a mental hospital, but as long as you did, and could not when you did not.
alacran
Posted 19 January 2022 - 06:38 AM
no no alacrán, I did accept the recommentations as long as it did (install), and could not (accept the recommendations) when it did not (install).
u r a car fixer and I am a car owner - I come 2 u and say that the car does not start, and u wrongly tell me that my car does start because it should start, and then I rightly reply that it should but it does not. we do agree that it should, the only disagreement is that u wrongly identify should with does, whereas should is used only because it does not and one wants it to do, and shouldn't is used only when it does and one does not want it to do.
back to the example, pls do spend one minute of ur time to get into ur head that I do not get paid to tell u or the world that something, even though it should, does not work. me, I would sooner it did work. one thing is certain, if it does not install properly, I am not going to click f8 and select disable signature enforcement everytime i boot just to second a dogma or please a dogma advocate.
so, if one tells u that it does not work, pls believe it as possible, not probable, sure or certain. so I am not asking for the sun and moon.
ur interpretation is amusing. !quién conociera a maría, amaría a maría!
te lo traduzco aquí: he aceptado los consejos hasta que se instaló correctamente, y no pude desde cuando no se instaló correctamente. dónde está mi locura en esto, sinceramente no lo sé. si me lo vas a explicar tú, a lo mejor voy a entenderlo.
Posted 19 January 2022 - 04:45 PM
Then, after a bunch of unnecessary words all your complain is:
You don't like the way used in Win_Debloat to install SVBus driver.
Why didn't you say it just like I did?, in plain English and not in obscure non understandable sentences.
Well, I'm agree with you. I also don't like the suggested way used in Win_Debloat and I do it at my own way.
What I usually do, just before apply Win_Debloat is:
Use BootIce to moddify the boot parameters of the Mini-10x64.vhd, into Internal (if exists) and external MBR and UEFI BCDs adding:
LoadOptionsString >>> DISABLE_INTEGRITY_CHECKS
AllowPrereleaseSignatures >>> True
Then after this I reboot and run Win_Debloat.
Doing it this way I don't need to use F8 key.
This is basically same boot parameters used by VHD_WIMBOOT when we create/install a new VHD.
NOTE: Works fine on Win10, not tested on Win11.
EDIT: For additional info to add this boot parameters with BootIce see this post and this post.
Maybe our friend wimb can implement this approach in Win_Debloat, perhaps as a separate option and a prerequisite before allow us install SVBus driver (only after verify the VHD booted with the right parameters).
alacran
Posted 19 January 2022 - 06:16 PM
alacrán, I do like everything, as I have no problems with errors, in that they are made to be corrected.
as for bootice I am sorry but I cannot use it in professional mode, unless I want horrible results.
so I do not think I can do what u did without proper guidance.
is there any way I can do it safely?
with win11 I have tried to make the yellow dot disappear from the partially installed svbus, but no dice.
Posted 19 January 2022 - 06:32 PM
u say windows 10, do u want my reality here? 9 times outta 10 svbus does not install properly on win10, unless I first install firadisk, and then, with firadisk installed I install svbus again, this time properly, and then I uninstall all of firadisk to get what one wants with svbus. now I am in ram thru firadisk and no issues with win11, and I presume 10 too, whereas when I have svbus installed and start the system in ram from a coldboot, it crashes a few times before not crashing anymore. if I do the same passing by a cold boot as filedisk and then reboot to ram, everything is ok.
I even told wimb about this a couple years ago, and I remember him telling me the same happened to him sometimes. now the problem is that the error is erratic, stochastic (now and then), not systematic (everytime).
Posted 19 January 2022 - 06:45 PM
so it is not the way svbus is installed, because, in my case at least, it is hardly ever installed by debloat or reduce or wimboot; the installation is only hinted at. the installation to which I allude is the one I try myself manually from any of these above, and when I do i try to reg either wimb's reg or yours, the one u provided quite recently when u said that the former does not always work. but I did so out of despair, as that yellow dot would never go away.
Posted 19 January 2022 - 06:48 PM
Add new boot parameters in BootIce is very easy:
Just open BCD edit in Professional mode, select the VHD, on the right pane on a free space make a right click and select New element and press once L key in your keyboard, the LoadOptionsString will be autoselected, acept and on next window add (you can use copy/paste) DISABLE_INTEGRITY_CHECKS
For AllowPrereleaseSignatures just make a right click and select New element and press A key in your keyboard 8 times untill you see AllowPrereleaseSignatures appear, acept and in next window select True/Yes.
Now you can close BootIce and reboot to run Win_Debloat and install SVBus driver on a fresh installed VHD (without requiring to use F8 key during boot).
That's all you need to know to make this work.
alacran
Posted 19 January 2022 - 07:46 PM
thanx a lot alacrán, and this cannot be done from a basic bootice window, must it necessarily be in professional mode?
btw, it was so easy... to follow ur instructions, but the svbus driver did not install in the end.
Posted 19 January 2022 - 09:03 PM
I prefer to do it in BootIce Professional mode, because the LoadOptionsString >>> DISABLE_INTEGRITY_CHECKS is applied only to the selected item (VHD in this case), if doing it in Easy mode it is into left pane and then it applies to everything you boot, and maybe you don't want this behaviour, see attached photo.
On 1 you can see if done in Professional mode, it is not applied to all items, but it is also possible to select it here on Easy mode.
On 2 you can see this setting applies only to the selected item no matter if done on Professional or Easy mode.
alacran
Posted 19 January 2022 - 09:20 PM
btw, it was so easy... to follow ur instructions, but the svbus driver did not install in the end.
Did you reboot after this and then after reboot ran Win_Debloat and followed its instructions to install SVBus driver, installing first EVRootCA.reg and latter run as admin instx64.exe?
Did you tried this in a fresh installed VHD with no previous intent or installation of firadisk or SVBus driver.
Because doing it this way never fails to me.
alacran
Posted 19 January 2022 - 10:51 PM
your last condition was not satisfied. let me try to see if I can do something about it.
well, at last, believe it or not, I have made it. oh no, sorry, I think I talked too soon. still no dice. in win11, firadisk needs no disabling, whereas svbus paradoxically needs disabling signature enforcement at bootup.
Posted 20 January 2022 - 05:32 AM
@alacran
@antonino61
What is the Date of your bootmgr file for MBR booting and your \EFI\Microsoft\Boot\bootmgr.efi for UEFI booting with Windows Boot Manager Menu ?
What I can say is that the usual tricks in BCD using bcdedit like "testsigning on" and "loadoptions DISABLE_INTEGRITY_CHECKS" and "nointegritychecks on" are not sufficient anymore.
Windows Boot Manager since August 2021 Additionally Requires now: On Boot Menu item press F8 for Advanced Menu and Select Disable driver signature enforcement
- Recent Windows Boot Manager - August 2021 - requires for SVBus driver to Disable Driver Signature Enforcement
Thanks to alacran solved by Load EfiGuard - Disable Windows Driver Signature Enforcement - Or on Boot Entry press F8 for Advanced and Select DSE
Grub2 has now as first menuentry to Load EfiGuard - Enter or wait 10 seconds to activate - Skip by selecting other entry
This works for all Windows entries in Grub2 Menu and the chainloaded UEFI Grub4dos (Grub4efi) Menu and the chainloaded Windows Boot Manager Menu.
See here for more Info on Recent Windows Boot Manager
Info for Online Install of SVBus driver:
- Win_Debloat will Install EVRootCA.reg for you.
- Manually you need to do:
Use R-mouse menu to Run as admin file instx64.exe of SVBus-signed_2 folder to Install SVBus driver
" Make Install of SVBus driver in VHD Effective " " Reboot First as FILEDISK - use F8 in Boot Manager Menu " " Requires to use F8 Disable driver signature enforcement " " Reboot is Required to Install the Changes "
Posted 20 January 2022 - 06:21 AM
@ wimb
You are right, I remember the info you quoted.
I'm using 10x64 2004 ISO to install on the Mini VHD, so all my files are from 2020, long before August 2021.
That explains why as I said I never had a problem installing SVBus driver on this version, and also as said I never tested Win11.
But the info in your post in no way includes or justifies the use of firadisk as antonino63 wants to do to try to solve this inconvenience.
EDIT: Las sentence was fixed IAW antonino63 last comment on next post
alacran
Posted 20 January 2022 - 06:38 AM
it seems to me that not using firadisk is more important than making the system work, and I would humbly like to know why in order to sympathise with the advocates of this tenet. I also told u that if I have svbus and cold-boot to ram 3 times outta 4 or 9 outta 10, I have issues (BSOD and the like); never has it happened with firadisk. now I can pledge I want the same situation with svbus, just to prove to anybody that I have no problem using svbus flawlessly. nobody but the circumstances make me prefer firadisk, I did not fall in love with either.
btw, instead of using firadisk in lieu of svbus, in the light of what wimb said, can we not swap this bootmgr for another of a previous date so as to make everybody happy?
@alacrán
when u say "antonino63 pretends to do", r u sure u do not mean "antonino61 wants to do"? just to avoid the confusion u want to shun, I might get things wrong, but I never pretend.
Posted 20 January 2022 - 06:48 AM
So IMHO 10x64 2004 also known as 20H1 is the best option to build a Mini-10x64.vhd, not only because it has less files to remove and you can get the smaller used size, without removing critical files, but also because SVBus driver installs very easily and without any issue in this version.
In fact it sounds a little crazy start with a newer version more bloated, and then remove more bloat, just to end with a same basic OS, if we want to build a Mini-10x64.vhd, and latter have troubles to install SVBus driver if we want to run it on Ram, we can avoid this issue since the begining installing version 2004 (20H1).
alacran
Posted 20 January 2022 - 06:53 AM
So IMHO 10x64 2004 also known as 20H1 is the best option to build a Mini-10x64.vhd, not only because it has less files to remove and you can get the smaller used size, without removing critical files, but also because SVBus driver installs very easily and without any issue in this version.
Sure that statement is valid for the Internal bootmgr and bootmgr.efi files .....
But you also have to deal with the External bootmgr and bootmgr.efi files which are Updated regularly and become of recent date ....
Pressing F8 in Boot Manager Menu remains important to boot VHD having SVBus driver.
Or in Grub2 Menu Load EfiGuard - Disable Windows Driver Signature Enforcement
Posted 20 January 2022 - 07:26 AM
No problem if updates are blocked, (as I do).
I only press F8 on Asus MB (or equivalent F7, F10 on other MB brands) to UEFI boot grub2 and/or grub4dos from second HD.
alacran
Posted 20 January 2022 - 07:57 AM
No problem if updates are blocked, (as I do).
Sure personal settings can work for you, but I have to give general requirements and instructions as support ....
Posted 20 January 2022 - 09:42 AM
Download File E = Encrypted PassWord = bootwimb - AntVirus Software and Windows Defender must be Disabled for working with signed SVBus driver !!
Update Manual: VHD_WIMBOOT.pdf - Download: Win10_2004_English_x64.iso and Win11_English_x64v1.iso
- Changed - remove_DLL_System32.txt - Instead of 1470 Unused DLL files now only 200 largest Unused DLL files are removed from System32
- Changed - remove_files_System32.txt - the about 200 KBD*.DLL files are now removed here always instead of Optionally by remove DLL files
I found that removing only 200 DLL files instead of 1470 is needed for support to Add Devices like Printer, Bluetooth + Speakers
So the idea is to Remove 200 files DLL + about 200 KBD*.DLL files to Save Space and Reduce Number of Files and to Keep functionality to Add Devices !
The present UEFI RAMDISK configuration is tested and working OK for Adding Printer, Bluetooth + Speakers, Activation and Network
Mini_2004_US.zip 160.98KB
1404 downloads and
Mini_11_US.zip 185.72KB
1293 downloads
Posted 20 January 2022 - 07:09 PM
Just tested Win_Reduce_Trusted-60 on Mini-10x64.vhd
This are my findings:
remove_files_System32.txt >>> works fine removing almost all Keyboards.
remove_DLL_System32.txt >>> works fine removing big size *.DLL files. But I can't save an image file in Paint after reduction, after checking (previous builds) I noticed this is not a new issue, sorry I didn't found it before in a previous version of Win_Reduce.
alacran
Posted 20 January 2022 - 08:27 PM
remove_DLL_System32.txt >>> works fine removing big size *.DLL files. But I can't save an image file in Paint after reduction, after checking (previous builds) I noticed this is not a new issue, sorry I didn't found it before in a previous version of Win_Reduce.
Thanks for testing May be we can use ProcMon and Process Explorer to find what file is missing and is causing Paint FileSave issue.
Posted 21 January 2022 - 04:46 AM
Just tested Win_Reduce_Trusted-60 on Mini-10x64.vhd
remove_DLL_System32.txt >>> works fine removing big size *.DLL files. But I can't save an image file in Paint after reduction, after checking (previous builds) I noticed this is not a new issue, sorry I didn't found it before in a previous version of Win_Reduce.
alacran
Required DLL file is \Windows\System32\shellstyle.dll
Editing remove_DLL_System32.txt file (line 1511) to:
; \Windows\System32\shellstyle.dll ; required for Paint fixed the issue.
alacran
0 members, 9 guests, 0 anonymous users