Windows 10: Any known reason why current NIS_FULL.EXE (64-bit) (v119.0.0.0) still contains an older...

Hello all,


is there any known reason why current NIS_FULL.EXE (64-bit) (v119.0.0.0) still contains an older mpsigstub.exe version (v1.1.14500.5) ?


Please note that I'm reporting this via this forum because :

- due to recent WDSI (Windows Defender Security Intelligence) web design changes from WDSI Updates(/Definitions) page it's no more possible to provide any quick direct feedback to WDSI support people via WDSI Updates(/Definitions) or even its latest WDSI Updates Change Log page,

- from a past issue I experienced (and directly reported via same involved WDSI Update(/Definitions) or WDSI Updates Change Log pages) I'm already aware that presence of an older mpsigstub.exe version may likely prevent Network Inspection System updates to install successfully,

- I've already provided this same feedback via a more generic MS Support Chat 2 days ago but enclosed mpsigstub.exe version (v1.1.14500.5) is still unchanged so I'm unsure if further MS internal reporting might be proceeding (also if knowing that chat case # should be needed for any reason , then please just let me know).


P.S. If a better or more direct way to report this kind of issue should exist, then please just let me know as well.

P.P.S. JFYI because MS Security Essentials failed to self update to v1.273.330.0 (due to 'Running X86 MpSigStub.exe on an X64 machine' and 'ERROR 0x80070645' from MpSigStub.Log) I'm happy to also confirm everyone that forcing another self update to latest current v1.273.334.0 indeed worked perfectly.


Best Regards

Rob

:)

 

Raid 0 help

Hi all, I've followed the IRST raid installation directions and I have created myself a Raid 0 volume. Rapid storage confirms my successful migration from a system disc to a raid 0 array. I'm also able to select it as my boot device in BIOS, but what I don't understand is why it is not listed in my Drives under my computer

In fact, my computer still lists my original C: drive with the original capacity. I feel as if I've miss an important step here and I'm unsure how to proceed.

 

Windows 10 Raid 0

Before my Windows 10 Pro 64 Bit Installation, I went into my Motherboard's BIOS and set my two 2TB hard drives in Raid 0 formation. After my Windows 10 Installation, "this computer" sees my "C" drive as only 2TB. Windows 10 should recognize my Raid 0 "C"
drive capacity as 4TB. Why is windows 10 listing my "C" drive as 2TB? Windows 10 should have spanned the Installation across my two hard drives in RAID 0 formation. Did Windows 10 install only onto one hard drive? How can I correct this Windows Installation
to span across my two Seagate SSHD hard drives in RAID 0 formation?

 

Raid 0 help

You need to resize your NTFS partition. Run (Super + R; the run dialog box) and execute "diskmgmt.msc". You'll see that your RAID-0 is only partitioned to half of the array's size. Converting a disk to RAID doesn't do anything to the size of your partitions.