Jesus! It worked! I put all .sys and .inf files from Win10Ent to a directory. Then I replaced "NTamd64...1" with "NTamd64...3" in inf files. That was it, everything is functional! Was /dism commands necessary Xinso?
T-S, with all due respect, I will disagree. Who makes you an expert to know my system better than I do? * Do you have Alieneware 17 R3 (so that you can verify Toshiba stack not turning off radio permanently upon exit)? * Do you have Microsoft BT Mouse 3600 (so that you can verify Toshiba stack is working with it)? * Did you have a Microsoft Sculpt BT mouse (to measure that Toshiba stack does not consume more energy)? 1 year all my Blue s/h/i/t devices work without a single problem on Win10Ent. And yes Toshiba turned off my radio permanently upon exit, yes it consumed more power (in fact it ate 1.5 hours from my battery life when testing), and MS 3600 mouse does not work with it. Here is a link for you as an example that it does not work (remove ###): https###://forum.toshiba.eu/showthread.php?94188-Toshiba-Bluetooth-stack-not-working-with-Microsoft-Bluetooth-mobile-mouse-3600 What does this have to do with Gaymerica now? And where did that conspiracy theory come from? I don't care if MS is American or Martian. I use technology to make money and make my life easier. Nobody is paying me money to waste my time being their fanboys.
Obviously I can't talk for every piece of HW, especially crap MS' ones, I'm just sharing my experience, which is above the average given my work and given the early adoption of BT here in europe. No, I don't mind to buy such things. I'm used to good pointing devices and keyboards, that excludes automagically anything built by MS. Ok You have a buggy mouse, that possibly works better with the ugly MS stack, that doesn't make the Toshiba stack worse. You are facing a corner case, that's all.
Can anyone please share the HP Unified Write Filter Configuration App from HP Thin Clients with Windows 10 IoT Enterprise?
Pal, you gotta chill. Your animosity towards Americans seems to have clouded your judgement about Microsoft. Microsoft makes great mice. Microsoft Wireless Mobile Mouse 4000 is my fav since 10+ years. 1) It works EVERYWHERE .... including glass! Sofa, desk, wall, blanket... Thanks to Bluetrak, it just works. There is no other mouse like it. 2) It is the QUIETEST. Great tactile feedback, silent. Anything else is at least twice louder And you call it crap and look down on me for using it? I also do not like you condescending tone abbout Alienware: 1) It has beautiful 17.3" 4K IGZO screen 2) It has 1TB PCI-E NVMe SSD that does 2,600 MB/s. 3) It has a great non-chicklet keyboard that is impossible to find on any other laptop 4) It has a 96 WH battery that gives me almost 9 hours of usage. 5) It is silent. No fan ever during regular use. So tell me again what basis do you have for your condescending tone for a laptop that weighs 3.5 kgs and gives me 9 hours of continuous usage on a 17" screen without sounding like a rocket launchpad? Do you have an alternative? Because I sure as hell could not find one, and I tried many. I have no idea what your work is or what importance you are supposed to have to know everyone's hardware better than they do. But I will suggest you leave your prejudices aside and let people be if you do not have anything tangible to offer to their quest. So far you have nothing to offer for mine.
@countingcrows How is your Bose Bluetooth QuietComfort 35 Stereo going now? Is it working good with the drivers from Windows 10? Have you tried the ones from Windows Server 2016? Now I use Windows 8.1 Embedded Lockdown Manager for Windows 10 Unified Write Filter. But I am looking for GUI-based UWF manager App from Thin Clients with Windows 10 IoT Enterprise. So hard so far.
Xinso, all is well. I don't think DISM was necessary at all. I will test this. I don't think I needed anything from Win10 install. I just needed to copy all these files to a directory and modify NT string. Because even the ones on server (in FileRepository) have old NT strings for workstation. Driver Signing Enforcement... I can't get this permanently off. I have Secure Boot off and modified BCD but still I had to do a manual F8 to choose from menu when installing the modified inf. Is there anything I can do for your request? Where do I search on Win10 for what you are looking for?
Good on you. Thank you for your kind offer. I am just dreaming for a UWF manager from Thin Clients' Windows 10 IoT Enterprise. But it is to no avail 'till now. No worries, mate. I am just dreaming...
T-S, let's peace out. You have been helpful on another aspect as "diskperf -y" was what I am looking for. Thanks!
Bose QuckConnect 35 Bluetooth HowTo On Windows Server 2016 Here is how I got this working: 1) After powering on machine, press F8 how to get to startup options. Choose "Disable Driver Signature Enforcement". 2) Search for these files in \windows directory (get the ones in inf, system32/drivers, FileRepository) and copy them to new directory. Code: btampm.inf BtaMPM.sys BthA2DP.sys bthaudhid.inf BthAvrcpTg.sys BthHfAud.sys BthhfHid.sys drmk.sys drmkaud.sys ks.inf ksthunk.sys MsApoFxProxy.dll mshidkmdf.sys portcls.sys SysFxUI.dll wdmaudio.inf wdmaudio.PNF wdma_bt.inf WMALFXGFXDSP.dll Probably only a subset will do but still this is the list from Win10Ent install. 3) Open all .inf files and replace all occurences of: "NTamd64...1" with "NTamd64...3". I think only 2 of them has those. 4) Device Manager > Other Devices > Bluetooth Peripheral Device. Point to the directory with all these files. There are 2 of these devices, do for both. It will ask to confirm unsigned device, choose install. These should show now: Sound, Video and Game Controllers: Bose QuietComfort 35 Stereo Human Interface Devices: Bose QuietComfor 35 Audio/Video Remote Control HID That is it. NB: Another device called "Hands-Free Unit" does not install even all its files are in that directory. It is supposed to shows as "Bose QuietComfort 35 Hands-Free" under Sound, Video and Game Controllers. This is probably because "Bluetooth Hands Free Service" is missing from Server install. Since I don't use it, I did not bother installing the service. I will check this later. NB2: No dism commands were necessary.
All okay with Windows Server except few items. 1) Where is msconfig/task manager>startup item? msconfig was especially convenient instead of going through 20 registry places. 2) Windows Spotlight: Any possibility to get this going? I will get to SQL Server 2016, ADFS, Dynamics CRM Server 2016 later. They work fine on a VMware setup.
It never had a specific package or identified feature, just workable with dism Spoiler Create WimBOOT images: • Copy the install.wim from mounted iso to a new file. You'll use this copy of the file to create your WIMBoot image. Code: md C:\Images Copy F:\sources\install.wim C:\Images\install.wim • Separate the Windows RE image from the main Windows image Code: md C:\mount Dism /Mount-Image /ImageFile:C:\Images\install.wim /Index:1 /MountDir:C:\mount Code: attrib -S -H -I C:\mount\Windows\System32\Recovery\winre.wim move C:\mount\Windows\System32\Recovery\winre.wim C:\Images\winre.wim Code: Dism /Image:C:\mount /Optimize-Image /WIMBoot Code: Dism /Unmount-Image /MountDir:C:\mount /Commit Code: Dism /Export-Image /WIMBoot /SourceImageFile:C:\Images\install.wim /SourceIndex:1 /DestinationImageFile:C:\Images\install_wimboot.wim /CheckIntegrity DEL /F /Q C:\Images\install.wim REN C:\Images\install_wimboot.wim install.wim
I ask You: How to uninstall or remove windows sidebar 10.0.14393.0 C:\Program Files\Windows Sidebar C:\Program Files (x86)\Windows Sidebar WindowsApps 10.0.14393.0 C:\Program Files\WindowsApps in windows 2016? thanks.
CAN I uninstall or remove Windows Media Player 32bit only C:\Program Files (x86)\Windows Media Player, and keep 64bit C:\Program Files\Windows Media Player? How to? OR If I used the MSMG ToolKit, CAN I remove Windows Media Player 32bit, and keep 64bit only? Thanks. (Sorry, My english is to bad)
The x86 is mergered in amd64 package - Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.14393.0: Code: amd64_microsoft-windows-m..age-base-deployment_31bf3856ad364e35_10.0.14393.0_none_e5f2baba47b6f571.manifest amd64_microsoft-windows-m..ckage-ua-deployment_31bf3856ad364e35_10.0.14393.0_none_539ff14759520c6c.manifest amd64_microsoft-windows-m..player-mp3-settings_31bf3856ad364e35_10.0.14393.0_none_e5270ecb7829d409.manifest amd64_microsoft-windows-m..player-shellpreview_31bf3856ad364e35_10.0.14393.0_none_ee123eac89ea0517 amd64_microsoft-windows-m..player-shellpreview_31bf3856ad364e35_10.0.14393.0_none_ee123eac89ea0517.manifest amd64_microsoft-windows-m..player-wmpfileassoc_31bf3856ad364e35_10.0.14393.0_none_7a9926293ef7e69e.manifest amd64_microsoft-windows-m..yer-sideshow-gadget_31bf3856ad364e35_10.0.14393.0_none_559e0e68c5a4c554 amd64_microsoft-windows-m..yer-sideshow-gadget_31bf3856ad364e35_10.0.14393.0_none_559e0e68c5a4c554.manifest amd64_microsoft-windows-media-player_31bf3856ad364e35_10.0.14393.0_none_cdd1f7d39ebca861.manifest amd64_microsoft-windows-mediaplayer-autoplay_31bf3856ad364e35_10.0.14393.0_none_486f1c1956ad6444 amd64_microsoft-windows-mediaplayer-autoplay_31bf3856ad364e35_10.0.14393.0_none_486f1c1956ad6444.manifest amd64_microsoft-windows-mediaplayer-common_31bf3856ad364e35_10.0.14393.0_none_979cee077c9c35fe.manifest amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_10.0.14393.0_none_38de2e9a65cc5dfc amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_10.0.14393.0_none_38de2e9a65cc5dfc.manifest amd64_microsoft-windows-mediaplayer-deployment_31bf3856ad364e35_10.0.14393.0_none_9f4b3d065a760cea.manifest amd64_microsoft-windows-mediaplayer-playlists_31bf3856ad364e35_10.0.14393.0_none_d859006dd3e5b398.manifest amd64_microsoft-windows-mediaplayer-setup_31bf3856ad364e35_10.0.14393.0_none_db6834fced3d7e54 amd64_microsoft-windows-mediaplayer-setup_31bf3856ad364e35_10.0.14393.0_none_db6834fced3d7e54.manifest amd64_microsoft-windows-mediaplayer-shortcut_31bf3856ad364e35_10.0.14393.0_none_dc45ddbf646801ed amd64_microsoft-windows-mediaplayer-shortcut_31bf3856ad364e35_10.0.14393.0_none_dc45ddbf646801ed.manifest amd64_microsoft-windows-mediaplayer-skins_31bf3856ad364e35_10.0.14393.0_none_d6d58da4f0256ebb amd64_microsoft-windows-mediaplayer-skins_31bf3856ad364e35_10.0.14393.0_none_d6d58da4f0256ebb.manifest amd64_microsoft-windows-mediaplayer-vis_31bf3856ad364e35_10.0.14393.0_none_9e5e840dd9b88f4f amd64_microsoft-windows-mediaplayer-vis_31bf3856ad364e35_10.0.14393.0_none_9e5e840dd9b88f4f.manifest amd64_microsoft-windows-mediaplayer-wmerror_31bf3856ad364e35_10.0.14393.0_none_64c95e68cda911f9 amd64_microsoft-windows-mediaplayer-wmerror_31bf3856ad364e35_10.0.14393.0_none_64c95e68cda911f9.manifest amd64_microsoft-windows-mediaplayer-wmpdxm_31bf3856ad364e35_10.0.14393.0_none_d1ac8ed53e7e2d7e amd64_microsoft-windows-mediaplayer-wmpdxm_31bf3856ad364e35_10.0.14393.0_none_d1ac8ed53e7e2d7e.manifest amd64_microsoft-windows-mediaplayer-wmpeffects_31bf3856ad364e35_10.0.14393.0_none_26c252c2a624578f amd64_microsoft-windows-mediaplayer-wmpeffects_31bf3856ad364e35_10.0.14393.0_none_26c252c2a624578f.manifest amd64_microsoft-windows-mediaplayer-wmplayout_31bf3856ad364e35_10.0.14393.0_none_65c9cc1f77b48a25.manifest amd64_microsoft-windows-mediaplayer-wmpps_31bf3856ad364e35_10.0.14393.0_none_dbfebb5352afeb34 amd64_microsoft-windows-mediaplayer-wmpps_31bf3856ad364e35_10.0.14393.0_none_dbfebb5352afeb34.manifest amd64_microsoft-windows-mediaplayer-wmpshell_31bf3856ad364e35_10.0.14393.0_none_393bc5335c01751b amd64_microsoft-windows-mediaplayer-wmpshell_31bf3856ad364e35_10.0.14393.0_none_393bc5335c01751b.manifest amd64_microsoft-windows-windowsmediaplayer-adm_31bf3856ad364e35_10.0.14393.0_none_9df1645733ee1542 amd64_microsoft-windows-windowsmediaplayer-adm_31bf3856ad364e35_10.0.14393.0_none_9df1645733ee1542.manifest Microsoft-Windows-MediaPlayer-Package-base~31bf3856ad364e35~amd64~~10.0.14393.0.cat Microsoft-Windows-MediaPlayer-Package-base~31bf3856ad364e35~amd64~~10.0.14393.0.mum Microsoft-Windows-MediaPlayer-Package-ua~31bf3856ad364e35~amd64~~10.0.14393.0.cat Microsoft-Windows-MediaPlayer-Package-ua~31bf3856ad364e35~amd64~~10.0.14393.0.mum update.cat update.mum wow64_microsoft-windows-m..player-shellpreview_31bf3856ad364e35_10.0.14393.0_none_f866e8febe4ac712 wow64_microsoft-windows-m..player-shellpreview_31bf3856ad364e35_10.0.14393.0_none_f866e8febe4ac712.manifest wow64_microsoft-windows-m..player-wmpfileassoc_31bf3856ad364e35_10.0.14393.0_none_84edd07b7358a899.manifest wow64_microsoft-windows-media-player_31bf3856ad364e35_10.0.14393.0_none_d826a225d31d6a5c.manifest wow64_microsoft-windows-mediaplayer-autoplay_31bf3856ad364e35_10.0.14393.0_none_52c3c66b8b0e263f wow64_microsoft-windows-mediaplayer-autoplay_31bf3856ad364e35_10.0.14393.0_none_52c3c66b8b0e263f.manifest wow64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_10.0.14393.0_none_4332d8ec9a2d1ff7 wow64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_10.0.14393.0_none_4332d8ec9a2d1ff7.manifest wow64_microsoft-windows-mediaplayer-deployment_31bf3856ad364e35_10.0.14393.0_none_a99fe7588ed6cee5.manifest wow64_microsoft-windows-mediaplayer-wmpdxm_31bf3856ad364e35_10.0.14393.0_none_dc01392772deef79 wow64_microsoft-windows-mediaplayer-wmpdxm_31bf3856ad364e35_10.0.14393.0_none_dc01392772deef79.manifest x86_microsoft-windows-m..player-mp3-settings_31bf3856ad364e35_10.0.14393.0_none_89087347bfcc62d3.manifest x86_microsoft-windows-mediaplayer-common_31bf3856ad364e35_10.0.14393.0_none_3b7e5283c43ec4c8.manifest x86_microsoft-windows-mediaplayer-playlists_31bf3856ad364e35_10.0.14393.0_none_7c3a64ea1b884262.manifest x86_microsoft-windows-mediaplayer-setup_31bf3856ad364e35_10.0.14393.0_none_7f49997934e00d1e x86_microsoft-windows-mediaplayer-setup_31bf3856ad364e35_10.0.14393.0_none_7f49997934e00d1e.manifest x86_microsoft-windows-mediaplayer-skins_31bf3856ad364e35_10.0.14393.0_none_7ab6f22137c7fd85 x86_microsoft-windows-mediaplayer-skins_31bf3856ad364e35_10.0.14393.0_none_7ab6f22137c7fd85.manifest x86_microsoft-windows-mediaplayer-vis_31bf3856ad364e35_10.0.14393.0_none_423fe88a215b1e19 x86_microsoft-windows-mediaplayer-vis_31bf3856ad364e35_10.0.14393.0_none_423fe88a215b1e19.manifest x86_microsoft-windows-mediaplayer-wmerror_31bf3856ad364e35_10.0.14393.0_none_08aac2e5154ba0c3 x86_microsoft-windows-mediaplayer-wmerror_31bf3856ad364e35_10.0.14393.0_none_08aac2e5154ba0c3.manifest x86_microsoft-windows-mediaplayer-wmpeffects_31bf3856ad364e35_10.0.14393.0_none_caa3b73eedc6e659 x86_microsoft-windows-mediaplayer-wmpeffects_31bf3856ad364e35_10.0.14393.0_none_caa3b73eedc6e659.manifest x86_microsoft-windows-mediaplayer-wmplayout_31bf3856ad364e35_10.0.14393.0_none_09ab309bbf5718ef.manifest x86_microsoft-windows-mediaplayer-wmpps_31bf3856ad364e35_10.0.14393.0_none_7fe01fcf9a5279fe x86_microsoft-windows-mediaplayer-wmpps_31bf3856ad364e35_10.0.14393.0_none_7fe01fcf9a5279fe.manifest x86_microsoft-windows-mediaplayer-wmpshell_31bf3856ad364e35_10.0.14393.0_none_dd1d29afa3a403e5 x86_microsoft-windows-mediaplayer-wmpshell_31bf3856ad364e35_10.0.14393.0_none_dd1d29afa3a403e5.manifest To my best knowledge, you can only manually remove it by deleting Files and Registries according to those wow64 and x86 manifest. Try to learn extracting a package yourself.