Get or Set-WebConfiguration and Get or Set-WebConfigurationProperty does not work for 32-bit applications when pspath is 'MACHINE/WEBROOT'
When configuring IIS using Powershell, the cmdlets that read or write to configuration do not work when the application pool is 32-bit.
There is no way of specifying the "bitness" of the application therefore by default the configuration is written to the web.config file in the Framework64 folder which is ignored for 32-bit applications.
This is also the case for IIS manager when using "Configuration Editor". You can choose the location of "Root Web.Config <location path="my website"> however this ignores whether the application is 32 or 64 bit and always writes to the 64 bit location in the Framework64 folder.
On many cmdlets it is possible to specify the clr version however this does not help when the application is 32-bit.