This is not at all what he is saying. You should respond to USB requests, not place structures in specific places on the internal system memory.
Windows, seeing VID: PID: Serial for the first time, will request the OS string descriptor at index 0xee. The device should respond with a data packet that matches the structure format you specified. If everything in the returned descriptor is correct (your example looks good), Windows will then issue a device provider request with bReq set to what you specified in the string descriptor response as MS_VendorCode (0x04 in your example).
If your device responds with the correct OS function descriptor, then magic happens. The magic that people usually want is that their device uses the winusb driver without providing the .inf file.
Please note that this request is executed only once. If you are designing a device, you usually want to do this many times. To do this, you need to remove the device from the device manager, and then in regedit, find your VIDPIDRELEASE under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags and delete it. Now, when you reconnect your device, it will execute this operating system descriptor request again.
For more information, refer to https://github.com/pbatard/libwdi/wiki/WCID-Devices , this is much clearer than the documents provided by MS.
source share