# The Wiert Corner – irregular stream of stuff

• ## Email Subscription

Join 1,640 other followers

# Archive for the ‘Windows Server 2003 R2’ Category

## WannaCry — Decrypting files with WanaKiwi + Demos – Comae Technologies

Posted by jpluimers on 2017/05/19

[Archive.is] Working Windows XP & 7 demos. #FRENCHMAFIA: WannaCry — Decrypting files with WanaKiwi + Demos – Comae Technologies:

### TL;DR;

DO NOT REBOOT your infected machines and TRY wanakiwi ASAP*!

*ASAP because prime numbers may be over written in memory after a while.

Via:[WayBack] A French researcher says he’s found a tool that could help some fraction of victims running that older Windows version. Just don’t reboot!  WannaCry Ransomware Victims Might Have Some Hope–If They’re on Windows XP | WIRED

–jeroen

## Two Quick Methods for Finding Shared Folders in Windows

Posted by jpluimers on 2017/05/01

In addition to the two methods mentioned at Two Quick Methods for Finding Shared Folders in Windows (use net share or compmgmt.msc) I like this one:

fsmgmt.msc

It directly gets you to the “Shared Folders” inside compmgmt.msc

–jeroen

## permissions – recursively change owner windows 7 – Super User

Posted by jpluimers on 2016/10/27

Slightly updated the answer the /D Y part will recursively accept taking ownership when directory listing is denied in the permissions:

To fix really broken permissions, the best is to run these two commands one after the other:

takeown /F /D Y "C:\path\to\folder" /R
icacls "C:\path\to\folder" /reset /T

The first one will give you ownership of all the files, however that might not be enough, for example if all the files have the read/write/exec permissions set to “deny”. You own the files but still cannot do anything with them.

In that case, run the second command, which will fix the broken permissions.

–jeroen

## Batch files to show the User/System environment variables stored in registry – via: Stack Overflow

Posted by jpluimers on 2016/09/20

I wrote two tiny batch files that would dump the environment variables from the registry.

Various reasons:

1. Environment variables can be stored in two contexts: System and User (SET will show them all at once and for instance combine PATH up to 1920 characters).
2. Environment variables can be set to auto-expand or not, which you cannot see from a SET command (REG_EXPAND_SZ versus REG_SZ).

show-user-environment-variables.bat:

reg query "HKCU\Environment"

show-system-environment-variables.bat:

reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment"

Filtered results:

## 4K/5K monitors: when your RDP session has small black bands limiting the height/width to 2048/4096 pixels

Posted by jpluimers on 2016/08/29

Sometimes RDP limits you to 2048 pixels vertical (or 4096 pixels horizontal)

Just found out why on some Windows versions, the RDP sessions form my 4K monitor has some small black bands on top/bottom: older versions of Windows limit their RDP server to 4096 x 2048.

A 4K monitor will not hit the width limit (as 4K cheats: it is usually “just” 3840 pixels wide), but it does hit the height limitation (2160 is slightly more than 2048: you miss 112 pixels that show as two small black bands).

A 5K monitor is worse: it will hit both limits (5K does not cheat: at 5120 × 2880 it is exactly 5*1024 pixels wide) so you miss 124 pixels horizontally and a whopping 832 pixels vertically.

Don’t buy a 5K monitor yet if you do a lot of RDP work to older Windows versions.

The link below has a table listing various Windows versions, but it omits end-of-life versions so I’ve done some testing: Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2003 R2 share the same limitations as Windows Server 2008 most likely because their latest service packs share the same RDP 6.1 version.

I updated this in the table: