cluberti/vdi

Repository for VDI scripts

VDI

Repository for VDI scripts

The ConfigAsVDI.ps1 script at the root of this project is currently designed for Windows 10 Enterprise installations only - this has only been tested on Enterprise, and as such it is not guaranteed to work on Pro, Home, Education, LTSB, or any other variant of Windows 10. If you want to try, remove the version check at the beginning of the script. As always, this is as-is - if you break it, you get to keep the pieces.

The Windows 7 and Windows 8 versions of this script are stored here for archival/reference purposes, and will not be further updated.

vdi's Issues

Problem with "Run as administrator"

I tried the Windows 10 version, and it works fantastic except that I no longer have the ability to do “run as administrator” from the start menu, it appears that consent.exe fires but it never pops up on the screen. It is running in task manager but never opens on screen.

It also seems to have issue with shutdown, if you say restart it instantly goes to spinning circle and Please wait that is displayed normally after logging on.

I am attempting to use this on the Enterprise anniversary update version. Any ideas which option could be raising problems with the “run as” function?

Crash Dump settings

As far as I can see, you are not disabling memory dump creation. You are enabling it with a value of 0x1 which is enabling it with the full memory dump setting.

https://support.microsoft.com/en-us/help/254649/overview-of-memory-dump-file-options-for-windows

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl
CrashDumpEnabled REG_DWORD 0x0 = None
CrashDumpEnabled REG_DWORD 0x1 = Complete memory dump
CrashDumpEnabled REG_DWORD 0x2 = Kernel memory dump
CrashDumpEnabled REG_DWORD 0x3 = Small memory dump (64KB)

CrashDumpEnabled REG_DWORD 0x7 = Automatic memory dump

Additional registry values for CrashControl:
0x0 = Disabled
0x1 = Enabled

Running windows update in it's own process can cause it to fail

sc.exe config wuauserv type= own can cause Windows Update to fail to find updates, giving the error "There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070006)"

I had this issue and resolved it by switching the windows update service back to shared as described in this link: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/there-were-some-problems-installing-updates/8116d20a-4151-4132-9b91-ac0d6ae2d559?page=2#LastReply

The VDI script shouldn't change this from the default.

Power Scheme mismatch

You set the power scheme to High Performance pretty early on. Later on, you do the hard disk timeouts, but the GUID you use is for the Balanced power scheme and not the High Performance power scheme.

Script causing GINA gone in 14393.321 (RS1)

Script works fine for any Win10 before RS1. For RS1,

1. GINA will be gone.
2. If a user RDP into the VM, the login process will loop forever, login never get done.

It can be fixed by not touching the following service,

Write-Host "Disabling Device Association Service..." -ForegroundColor Cyan

Set-Service DeviceAssociationService -StartupType Disabled

Microsoft.Messaging Not Removed

Hello, I am running Win10 1511 and when running the current version of the script, I have to run it twice to fully remove Microsoft.Messaging. Just wanted to let you know that this is an issue in case that wasn't as designed.

Rename folder failed in File Explorer if enable "OneDrive" removal

OS: 14393.321
If enable "Remove OneDrive", reboot, right click and create a New Folder. You can never rename this New Folder to anything else from the Explorer. It works fine with cmd.

Problem seems caused by these two lines

Remove-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A52BBA46-E9E1-435f-B3D9-28DAA648C0F6}' -Recurse
Remove-Item -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{A52BBA46-E9E1-435f-B3D9-28DAA648C0F6}' -Recurse

---

Also, these two lines will return, "Set-ItemProperty: Cannot find drive. A drive with name 'HKCR' does not exist"

Set-ItemProperty -Path 'HKCR:\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}' -Name 'System.IsPinnedToNameSpaceTree' -Value '0'
Set-ItemProperty -Path 'HKCR:\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}' -Name 'System.IsPinnedToNameSpaceTree' -Value '0' 

---

DsmSvc service

If you Disable this service you can't setup any printer. There will be no print devices in the control panel. So be careful with services. This service should be enabled.

Write-Host "Disabling Device Setup Manager Service..." -ForegroundColor Cyan
Set-Service DsmSvc -StartupType Disabled